Command-line specification

Planned. RegesARC 0.0.1 has no supported user-facing CLI. Developer npm scripts build and launch the application; they are not an inference CLI. There is no verified executable command syntax to install or run from this page.

Intended operations

Operation family	Required behavior
Inventory and inspect	Exact artifact files, metadata, warnings and machine-readable identity
Plan	Explicit context/placement, assumptions and capacity errors
Load/unload	Applied settings, instance ownership, conflicts and terminal state
Chat	Interactive and bounded noninteractive streaming with cancellation
Download	Immutable complete files, resumable jobs and integrity commitment
Service management	Distinguish owned private instances from selected shared services
Diagnostics	Sanitized export with explicit destination and useful exit codes

These are requirements, not a command reference. Final verbs, flags and defaults should be documented only after a real parser and release binary exist.

Scriptability

Offer stable JSON output separately from human-readable progress. Send progress to the appropriate stream, preserve structured errors and use documented nonzero exit codes. Prompts and credentials must not be printed by default or passed in a form likely to leak through process listings.

Cancellation must propagate from terminal signals and wait for cleanup. A CLI exiting does not by itself prove that its model allocation or background service stopped. Model ownership and persistent daemon mode need distinct contracts.

Safe defaults

Do not download a different artifact, shorten context, prune experts, expose a network listener or stop another program silently. A confirmation-free script mode should still enforce the explicit scope supplied by the caller. Publish configuration precedence and profile isolation before encouraging automation.

Reference and release gate

LM Studio’s lms documentation covers its own model, daemon and server tooling. RegesARC should study the workflow without rebranding those commands as functional native features.

Qualification requires an actual distributed binary, parser tests, shell-safe examples, Windows signal behavior, cancellation/recovery, machine-readable outputs, version mismatch handling and cleanup receipts. Until then, use the native interface or the documented developer build scripts for their actual purposes.