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>
1 KiB
1 KiB
| kind | slug | title | plan_slug | status | priority | tenant_id | cursor_epic_id | updated_at |
|---|---|---|---|---|---|---|---|---|
| epic | fleet-dashboard | Fleet dashboard — all connected repos and convoys | automation-foundation | draft | P2 | global | null | 2026-07-03 |
Epic objective
Top-level fleet view: all convoys-<repo> workspaces (or connected repos) in one screen. Roll up convoys by status, gate inbox count, active agent_runs, recent spend by model alias.
Answers: “What needs me across all projects?”
In scope / out of scope
In scope
- Route
/fleetor home dashboard for operator account. - Cross-workspace tRPC (membership-scoped).
- Links into per-repo mission control (Epic 5).
Out of scope
- Multi-tenant fleet across unrelated customers (operator's own repos only for v1).
Dependencies
- Epic 4 (queryable convoy status).
- Epic 5 (gate semantics).
Acceptance criteria
- Operator with two connected repos sees combined “3 awaiting approval” badge.
Tasks
To be decomposed when epic graduates to ready.