Mission Control
Drive mission-control: MC product/control-plane QA
Track pickup in COLLAB and route unclear ownership immediately.
decision Typed actor collaboration templates defined — jiansen + codex
decision Elegant Actor Workflow v1 implementation slice def — jiansen + codex
decision R-008 upgrade control plane phase 2 landed — codex
decision R-008 registration/enrollment API contracts landed — codex
decision R-008 event ingestion and machine freshness landed — codex
decision R-008 pairing token contract landed — codex
+5 more in timeline below
1 decision waiting for you
action requiredGitHub annotation on Vibeful wrapper jobs 26017933766 and 26015833613: The job was not started because an Actions budget is preventing further use. The real release builds in Jiansen/vibeful-releases are separate: v0.2.46 real run 26015835891 succeeded and v0...
Project summary: green readiness · 0 active findings · 0 commits/24h
cd ~/Coding/mission-control && cursor agent --continueCodex reports on next automation heartbeat.or copy all Cursor commands: collab kickallTarget a role (builder/verifier) instead of a specific tool · Full Command → · / focus to
Fleet detail
| Actors | Kind | Runtime | Active Role | Proof | Queue Policy |
|---|---|---|---|---|---|
| codex@mission-control | agent | Codex | verifier | not configured | next-heartbeat-confirm |
| cursor@mission-control | agent | Cursor | builder | not configured | immediate-init |
Patrol Decision Detail: Drive mission-control: MC product/control-plane QAcodex · drive
Codex patrol is conservative on empty queue: if no self-block is present, wait for next heartbeat/re-read before initiating a new high-ROI task, unless board drift/security/authorized verification is obvious.
Track pickup in COLLAB and route unclear ownership immediately.
| Project | Readiness | Owner | Gates | Findings | 24h | Last |
|---|
mission-control
readyunknown @ unknown · 1d ago
Evidence (0 findings, no release)
🟢 多项目 COLLAB.md 聚合(vibeful + beefit) Command Center summary(needs-you / agent proof / project pulse / recent change / MC next action;legacy `/morning` route remains an alias only) Decision Queue + inline reply(写入 COLLA...
Recent Activity (last 6h) · 0 commits
No recent commits.
Control Plane Details (Runtime · VCP · Reconciliation · Dependencies · Stale Ownership)
0 active · 0 idle · 2 stale
Reports: 0 explicit · 0 fallback · 2 stale
Adoption: 0 need reports · 0 already routed · 0 unrouted
Command source: 0 need shared collab · 0 routed · 0 unrouted
Runtime rows prefer explicit agent reports from docs/agent-runtime.json + child .collab/runtime/reports.jsonl; repository activity and protocol files are fallback evidence only.⚠ 1 stale rule file(s) detected (>7d unchanged)
0 pending · 0 ready · 0 stale · 0 conflicts
Aggregates verification pipeline health by product journey. Shows which claims are stale, where evidence is missing, board conflicts, and untestable items blocked by upstream dependencies.
0 critical · 0 drive · 0 watch
Converts VCP conflicts, stale dependencies, ownership drift, and runtime-report adoption into one repair queue. These are MC infrastructure actions: fix the board, route the owner, or wait on an already-open Request.
0 ready · 0 blocked · 0 waiting
Converts `fixed_pending_verify`, `pending_codex_verify`, `claim`, and `verify` rows into an action list for Codex. Waiting rows need another owner to claim evidence first.
0 drive · 0 watch
Finds active rows without an accountable owner, actionable rows without a concrete next action, and closed rows that still look routed. Use the inline route form for single-row correction.
0 blockers · 0 edges · 0 blocked findings
Derived from each project's `blocked_by` / `blocking` fields. Use this to maintain dependency hygiene: unresolved upstreams, verified upstreams still referenced as blockers, and high-impact roots should be fixed or rerouted first.
unknown @ unknown
🟢 多项目 COLLAB.md 聚合(vibeful + beefit) Command Center summary(needs-you / agent proof / project pulse / recent change / MC next action;legacy `/morning` route remains an alias only) Decision Queue + inline reply(写入 COLLA...
3 registered · 0 discovered
draft-ready
Build Mission Control as an agent ops console first, with a triage-board layer for handoffs. It should feel closer to Vercel project operations plus Linear/Sentry triage than to a generic analytics dashboard.
First viewport should expose the current patrol decision, Mission Control self-health, project registry/discovery, and cross-project risk. Project cards and queues sit below that, because the primary user question is "what needs driving now?" not "how many cards exist?"
Work Queues
Agent-to-Agent Requests
All agent coordination resolved — no pending requests.