git.stella-ops.org/docs/_archive/orchestrator-legacy/console.md

Orchestrator Console (DOCS-ORCH-33-002)

Imposed rule: Work of this type or tasks of this type on this component must also be applied everywhere else it should be applied.

Last updated: 2025-11-25

Views

• Run list: deterministic table sorted by startedUtc DESC then runId; filters by dagId, status, owner, time range.
• Run detail: step graph with topological order; shows status, attempts, duration, logs link, outputs hash.
• DAG catalog: shows published versions with signatures and enable/disable state.
• Queue health: per-tenant queue depth/age, retry counts, worker availability.

Actions

• Start run (select DAG/version, supply inputs JSON, optional run token).
• Cancel run (best-effort).
• Download artifacts/logs (tenant-scoped).
• Stream live updates (WebSocket) for selected DAGs/runs.

Accessibility & UX

• Keyboard shortcuts: f focus filter, r refresh, s start run dialog.
• All timestamps UTC; durations shown with tooltip raw ms.
• Color palette meets WCAG AA; status badges have icons + text.
• Loading states deterministic; no infinite spinners—show “No data” with retry.

Determinism & offline

• Client-side sorting mirrors API order; pagination uses stable page_token.
• Console operates against local WebService; no external CDNs; fonts bundled.
• Exports (runs, steps) available as NDJSON for air-gapped audits.

Safety

• Tenant enforced via session; cross-tenant DAGs hidden.
• No raw secrets displayed; logs redacted server-side.
• Run cancellation confirms and records rationale for audit.