Architecture Decision Records
Each ADR captures one architectural decision: the context that forced the choice, the alternatives considered, what was decided, and the consequences. ADRs are append-only — superseded entries stay in the source tree but are hidden from this index.
| ADR | Status | Date | Decision |
|---|---|---|---|
| ADR-001 | Accepted | 2026-04-09 | Observability Surfaces and Cost Attribution |
| ADR-002 | Accepted, amended | 2026-04-20 | PTY Cassette Transport for Harness Golden Masters |
| ADR-003 | Accepted, amended | 2026-04-20 | PTY Terminal Rendering and Screen Model |
| ADR-004 | Accepted | 2026-04-20 | Terminal Harness Build-vs-Buy Boundary |
| ADR-005 | Proposed | 2026-04-25 | Power-Based Routing Replaces model_routes |
| ADR-006 | Proposed | 2026-04-25 | Manual Overrides Are Auto-Routing Failure Signals |
| ADR-007 | Accepted | 2026-04-27 | Sampling Profiles Belong in the Model Catalog |
| ADR-008 | Accepted | 2026-05-05 | Service Package and Transcript Boundaries |
| ADR-009 | Proposed | 2026-05-09 | Routing Surface Redesign |
| ADR-010 | Accepted | 2026-05-11 | Reasoning Wire Form Belongs in the Model Catalog |
| ADR-011 | Proposed | 2026-05-12 | Cost-Based Routing With Quota Pools |
| ADR-012 | Accepted | 2026-05-11 | Per-Source On-Disk Cache for Discovery + Runtime Signals |