Submatter/plans/Plan-automation-foundation/Epic-mission-control-gates-ui/Epic-mission-control-gates-ui.md
Randall Stillwell 35def387ae docs(plans): add Autensa benchmark tasks to automation foundation roadmap
Map reliability, operator UX, and spend-control follow-ons onto epics 1–9
so worker, webhooks, and fleet work have bead-scale task briefs.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-03 10:48:36 -05:00

1.9 KiB

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 done P1 global null 2026-08-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

Follow-on tasks (Autensa benchmark)

Task Link
Convoy DAG visualization Task-convoy-dag-visualization
Automation tiers (supervised / semi-auto) Task-automation-tiers

Operator mid-build chat is tracked under Epic 7: Task-worker-operator-notes.