stella orchestrator — Command Guide
Audience: operators who inspect orchestrator jobs and runs from the CLI, including from air-gapped environments using cached ledger snapshots.
stella orchestrator reads job and run state from the Orchestrator API, or from preloaded run-ledger snapshots when offline. It reports only what the orchestrator returns — it never infers state — and surfaces provenance hashes and DSSE/attestation pointers when they are available.
Commands
stella orchestrator jobs list --output json|table [--offline]stella orchestrator jobs get --id <jobId> [--offline]stella orchestrator runs get --id <runId> [--offline]
Flags (common)
--offline: only allowed when cached ledger snapshots are available; otherwise exit code 5.--status,--type: filters for job listings; deterministic sort by created time then id.--output: json/ndjson/table.
Inputs/outputs
- Inputs: Orchestrator API or cached run ledger snapshots.
- Outputs: job/run metadata with provenance hashes and DSSE/attestation pointers when available.
- Exit codes per output and exit codes;
4for not found,5for an offline violation.
Determinism rules
- Sorted outputs; timestamps UTC; hashes hex lowercase.
- No inferred state beyond orchestrator responses.
Offline/air-gap notes
- Ledger snapshots must be preloaded; no live scheduler calls when
--offline.
