e256380671
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>
42 lines
1 KiB
Markdown
42 lines
1 KiB
Markdown
---
|
|
kind: epic
|
|
slug: fleet-dashboard
|
|
title: Fleet dashboard — all connected repos and convoys
|
|
plan_slug: automation-foundation
|
|
status: draft
|
|
priority: P2
|
|
tenant_id: global
|
|
cursor_epic_id: null
|
|
updated_at: "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 `/fleet` or 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`._
|