rstillwell/Submatter
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
Submatter/plans/Plan-automation-foundation/Epic-mission-control-gates-ui/Epic-mission-control-gates-ui.md
Randall Stillwell e256380671 plan(automation): add mission-control foundation backlog and model-routing ADR 
Documents the automation foundation plan (nine epics, Epic 1 taskified) and
the accepted model-provider registry contract. Updates .env.example for backlog
import workspace id and local/cloud AI provider env guidance.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-07 13:55:03 -05:00

1.4 KiB
Raw Blame History

kind slug title plan_slug status priority tenant_id cursor_epic_id updated_at
epic mission-control-gates-ui Mission control — convoy kanban, gate inbox, co-pilot automation-foundation draft P1 global null 2026-07-03

Epic objective

Echodo UI for human gates and convoy visibility:

  • Convoy kanban — columns map to state machine statuses (Planning, Awaiting plan approval, Building, …).
  • Gate inbox — “needs you” queue for convoy_review, pr_review, pre-released.
  • Approve / deny / request changes — calls transition_convoy_status with correct human-gate-* actor.
  • Gate co-pilot — AI panel using gate-copilot role route (resolveModel) to summarize plan/diff and suggest action.

In scope / out of scope

In scope

  • Routes under /{workspaceSlug}/convoys/ or /mission-control/.
  • Conductor-style chat to seed convoys (can call create_convoy MCP or web tRPC wrapper).

Out of scope

  • Fleet cross-repo view (Epic 9).
  • Unattended orchestration (Epic 6).

Dependencies

  • Epic 4 (lifecycle transitions and queryable convoy state).

Blocks

  • Epic 6 (orchestrator pauses until gate UI exists for dogfood).

Acceptance criteria

  • Operator sees pending Gate 1 convoy and approves → status ready.
  • Co-pilot uses claude-planning alias when configured.

Tasks

To be decomposed when epic graduates to ready.