Operator summary

Your command view over persisted orchestrator rows — bounded windows, not a live stream. Refresh to update counts; execution stays in the Python service. Use the global Flow strip in the header: Run → Review → Preview → Publish — then drill into a run or staging row for image and static output. From a graph run, open Live habitat (/habitat/live/{thread_id}) to watch the current working staging evolve — not a review snapshot.

What you are seeing. Aggregates from stored staging, publication, and graph_run tables only. Use Runs to find a graph run, Review for staging snapshots and previews, Publication for canon; optional identity_id filters tie the same lineage across surfaces. Where a row shows identity_id, follow its overview link for a compact cross-surface view.

Summary API not on this orchestrator build. Orchestrator GET /orchestrator/operator-summary is not available on this backend (route not implemented or wrong server).

Review queue

Staging snapshots by review action — window up to 500 recent rows (created_at).

0 need review
Ready for review
0
Ready to publish
0
Published (linked)
0
Other / not actionable
0

Open review queue →

Canon

Latest immutable publication in scope (same rule as publication index "current").

No current publication
Latest snapshot
—
Published at
—

Open publication →

Recent runs

Graph runs in the summary window (up to 0 loaded for counts).

No attention flag
Runs in window
0
Failed
0
Paused
0

Open runs →

Status / graph debug — orchestrator health and local inspection (developer-oriented).