# Mission Control — delivery timeline

Estimates assume one engineer familiar with the monorepo. Parallel work (UI + runner hardening) can compress calendar time.

| Phase | Scope | Estimate | Status (this PR) |
|-------|--------|----------|-------------------|
| **P0** | Workspace package, routing, TARDIS-themed shell, launchpad links | 1–2 days | **Done** |
| **P1** | Runbook JSON schema, catalog UI, help tooltips, GO button, POST `/api/runs` | 2–3 days | **Done** |
| **P2** | Allowlisted executor (bash + node), job store, SSE stream, live panels | 3–4 days | **Done** |
| **P3** | Touchpoint grading, compliance assertions, audit ZIP + checksums | 2–3 days | **Done** |
| **P4** | Vitest smoke test, docs, env knobs for Windows/Git Bash | 1 day | **Done** |
| **P5** | AuthN/Z (OIDC/API key), rate limits, queue (Redis) for multi-instance | 1–2 weeks | *Future* |
| **P6** | Map remaining `docs/**` runbooks to specs + narrow allowlist expansion | Ongoing | *Future* |

**Total (P0–P4):** roughly **9–13** engineering days for a production-capable v1 on a **trusted network**.

**Wall-clock if focused:** about **2 weeks** including review, hardening, and operator dry-runs on LAN.