Planner gate — Control Room v2 implementation plan
Planner gate for MC-4494: produce the implementation plan for Control Room Operating Model v2 rollout. Scope: - Read canonical docs: /home/lucienne/workspace/mission-control/do...
StateDoneNext ActionClosedOwnerLuciRuntimeClosedAge13d ago
Ticket is done; runtime is closed.·profile claude_opus_1m_medium · cwd /home/lucienne/workspace/mission-control · uptime 12d 19h · last activity 12d 16h ago
Description
MC-4495
Planner gate for MC-4494: produce the implementation plan for Control Room Operating Model v2 rollout.
Scope:
- Read canonical docs: /home/lucienne/workspace/mission-control/docs/control-room-operating-model.md
- Read visual explainer: /home/lucienne/workspace/mission-control/static/reports/control-room-interactive-explainer.html
- Convert Elmar's approved direction into a concrete implementation sequence.
Must include:
- Phases/tasks in safe order.
- Likely files/modules to inspect or modify.
- Acceptance criteria for each phase.
- Which role/gate owns each phase: Controller, Planner, Designer, Coder, Reviewer, Tester, Validator.
- Verification steps and rollback notes.
- Explicit reminder that runtime guidance is advisory; controller may override with any fitting capability.
Output:
- Planner handoff comment on this ticket and umbrella ticket.
- Do not implement code in this planning gate.
- Expected check-in: 2026-05-31 16:33:05 UTC.
Activity
done
INTERACTIVE
Luci is working...
Details —
Done
· High
· Luci
▼
SState
Done
Closed
PPeople
TTiming / Details▼
telegram (human)
Mission Control
13d ago
13d ago
Advanced / Operator evidence
RRouting owner
ROperator console
Ticket is done; runtime is closed.ticket_marked_doneprofile claude_opus_1m_medium · cwd /home/lucienne/workspace/mission-control · uptime 12d 19h · last activity 12d 16h agoMC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.
f3585f21-a874-47f1-967d-75b937d589b3 · luci · claude/anthropic/opus[1m]
Planner gate opened by Controller. Produce the implementation plan; no code changes in this gate.
Controller decision
planner13d ago
Planner handoff complete for Control Room v2 rollout.
Role: Planner
Runtime/capability: Hermes delegate_task planner subagent
Scope: Produce implementation plan only; no code/file/ticket mutations by planner.
Outcome: completed
Plan summary:
1. Phase 0 — Baseline/council preflight for workflow/runtime/comment dispatch behavior.
2. Phase 1 — Add inert 7-role registry and audit comment schema. No behavior change.
3. Phase 2 — Add active phase labels/metadata without status fragmentation or reassignment.
4. Phase 3 — Replace/augment WAT with Control Room role/gate surface.
5. Phase 4 — Make Controller dispatch explicit; role/comment actions notify Controller but do not auto-spawn stale/random runtimes.
6. Phase 5 — Notification model: event-driven comments/status changes to Controller; no_agent watchers as fallback.
7. Phase 6 — Scheduled task separation: Hermes cron for deterministic alerts, MC tasks for complex artifacts.
8. Phase 7 — Board/docs/runbook alignment and UI validation.
Likely implementation files:
- mission-control/models.py
- mission-control/app.py
- mission-control/mc_role_guidance.py
- mission-control/ticket_runtime.py
- mission-control/runtime_registry.py
- mission-control/templates/ticket_runtime_workbench.html
- mission-control/static/ticket_runtime_workbench.js
- board/home templates and JS as needed
- tests/test_workflow_pipeline.py
- tests/test_workflow_idempotency.py
- tests/test_ticket_runtime*.py
- tests/test_telegram_bridge.py
- tests/test_runtime_profiles.py
- new tests for Control Room roles/audit schema/comment-only role actions.
First safe implementation slice:
- Add canonical 7-role registry and audit comment formatter.
- Add tests for role keys, optional gates, old-role capability mappings, and audit schema formatting.
- Add read-only helper/API only if useful.
- Do not change dispatch, pickup, board, Telegram, or runtime behavior in this slice.
Acceptance highlights:
- Roles are gates/responsibilities, not mandatory separate workers.
- Ticket owner remains stable; active phase is label/metadata/comment trail.
- Elmar-facing board remains Inbox / Todo / Done.
- Runtime/model guidance remains advisory only; Controller may choose any suitable capability.
- Durable MC records include selected capability, evidence, and outcome.
Next step: Coder slice opened for the inert foundation. Reviewer/Validator gates required before behavior-changing phases.
lucienne13d ago
Controller gate: Planner gate completed. Deliverable: implementation plan produced and MC-4496 (Coder gate — inert 7-role registry and audit schema) spawned as first execution slice. Plan is grounded in docs/control-room-operating-model.md and the interactive explainer. Marking done.