Skip to content

Orchestrator Board

URL: https://claude.ai/artifact/REiaG4Kx3hBreKD5AKwSnw. It is private to the operator; published 2026-09-25 after the operator asked "Is there a place where we can see the overview of all these things".

The page is fixed. Its content lives in the artifact's own database, so the orchestrator updates records with the ArtifactData tool and never republishes the page for new data. Open views update live.

What it shows

  1. Summary strip: waiting on you / running / in review / done.
  2. Waiting on you: each open question with the orchestrator's recommendation, then later and answered items with what was done.
  3. Workstreams: cards grouped by state, each with a one-line now and next, links to issues and PRs, and who holds it (Mac Mini, claude-3, the operator, the Rig).
  4. Mac Mini jobs: model, effort, turns, peak context (as a share of the 1M window) and the orchestrator's verdict after re-checking the work (see Mac Mini delegation).

Data model

Access rule: the root reads at view and writes at admin, so only the owner and editors write. The page itself writes nothing.

Path Fields
meta/board updated (ISO), headline
streams/<id> title, state (running, review, you, scheduled, watching, done, blocked), owner (mini, me, you, rig), now, next, links ([{label, url}], https only), order, updated
asks/<id> question, recommendation, state (open, later, answered), answer, order
jobs/<name> name, task, model, effort, state (running, done, stopped), turns, peakK, verdict, started

Keeping it current

Whenever a PR merges, a Mac Mini job starts or finishes, or a decision is asked or answered: - update the matching document, pinning the write with if_version or using a batch; - bump meta/board.updated; - keep now and next to one sentence each.

scripts/mac-mini/job-facts.py gives each job's turns and peak context.

Ideas it suggests for Rig Cockpit (proposed 2026-09-25, not built)

  1. A "Needs you" inbox as the Cockpit's home view.
  2. A "waiting for" reason on every in-flight item.
  3. A run ledger with model, effort and outcome per agent.
  4. Freshness stamps.

The operator agreed to start with the inbox.