Milestone 4.E.3 — Phase 4 Exit Audit

Status: Planned
Goal: Track E — Exit Gate
Phase: 4 — Operator Platform & Multi-Provider
Estimated effort: 1 day
Track: Track E — Exit Gate

Why This Milestone Exists

Every prior phase's real completion evidence lived in a dedicated exit-audit artifact. Phase 4 adds a new human-facing attack surface (dashboard, multi-provider credentials) plus a second live upstream provider — it needs the same rigor as Phase 1's audit, not a lighter one.

Exit Criteria (10-point sign-off)

Second live LLM provider (Anthropic) passes same test depth as OpenAI
Registry.For(model) resolves both providers with zero handler/middleware changes
Circuit breaker and opt-in fallback verified via 4.E.2's fault-injection suite
Redis Lua hierarchical rate limiting passes concurrency over-admission test (zero tolerance)
Dashboard E2E suite (4.E.1) green in CI, required on main
Zero axe-core serious/critical accessibility violations
Management API OpenAPI spec consumed by dashboard client with zero manual type overrides
All Phase 1–3.5 regression suites green with 2 providers registered
Phase 4 gap register published with zero open P0 gaps
CURRENT_STATE.mdx and roadmap snapshot updated

Orientation (indicative)

Named paths, package layouts, libraries, schemas, env vars, and commands anywhere on this page are rough sketches for orientation — inspiration and a baseline, not a required change list.

During implementation, expect to:

open the live tree and follow existing patterns before inventing new ones
research current constraints (latency, tenancy, deploy shape, libraries) more deeply than this page can
advance the design beyond the sketch where measurement or code reality says so
land work in different filenames, merged packages, deferred docs, or new surfaces when the situation calls for it

Prefer outcomes over matching any particular file tree or command sequence.

Areas that may be involved (situational — not a checklist):

Operator dashboard
Provider abstraction / adapters
Evaluation / benchmarks

Success signals

Outcome-oriented signals that the milestone is in good shape. Exact filenames, package layouts, and commands may differ from any sketches above.

Gap register published using Phase 1's severity table format (P0–P3)
ADR fidelity table for every ADR touched in Phase 4
Zero open P0 gaps at sign-off
current-state.mdx updated to reflect Phase 4 completion

Prerequisites

All Track A–D milestones complete
Milestones 4.E.1 and 4.E.2 passing in CI