Skip to content

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.

ADRStatusDateDecision
ADR-001Accepted2026-04-09Observability Surfaces and Cost Attribution
ADR-002Accepted, amended2026-04-20PTY Cassette Transport for Harness Golden Masters
ADR-003Accepted, amended2026-04-20PTY Terminal Rendering and Screen Model
ADR-004Accepted2026-04-20Terminal Harness Build-vs-Buy Boundary
ADR-005Accepted2026-04-25Power-Based Routing Replaces model_routes
ADR-006Accepted2026-04-25Manual Overrides Are Auto-Routing Failure Signals
ADR-007Accepted2026-04-27Sampling Profiles Belong in the Model Catalog
ADR-008Accepted2026-05-05Service Package and Transcript Boundaries
ADR-009Accepted2026-05-09Routing Surface Redesign
ADR-010Accepted2026-05-11Reasoning Wire Form Belongs in the Model Catalog
ADR-011Accepted2026-05-12Cost-Based Routing With Quota Pools
ADR-012Accepted2026-05-11Per-Source On-Disk Cache for Discovery + Runtime Signals
ADR-013Withdrawn pending CONTRACT-0042026-05-14claude-tui PTY Harness as a Fork of claude
ADR-014Accepted2026-05-14Universal Harness Interface
ADR-015Accepted2026-05-15Browser Analytical Benchmark Workbench
ADR-016Accepted2026-05-16Cells Are Self-Describing Evidence
ADR-017Accepted2026-05-31Single Owner for middle→max Tier Escalation