This directory contains repository-wide architecture decisions that refine the accepted principles in Architecture Principles. Filenames remain descriptive, lowercase, and stable. ADR IDs are stable navigation labels; adding an ID does not rename an existing file or change its acceptance status.
The status in each ADR is canonical. This index is a discovery surface and must be updated in the same change when an ADR is added, accepted, superseded, or deprecated.
| ID | Decision | Status | Decision date | Scope |
|---|---|---|---|---|
ADR-0001 |
AI-Optimized Directory Structure | Proposed | 2026-07-16 | Directory ownership, artifact routing, migration gates, and target-directory activation |
ADR-0002 |
Developer Experience System | Proposed | 2026-07-31 | Journeys, federated contracts, projections, native evidence, governance, support, and DX measurement |
ADR-0003 |
Harness Run Evidence Bridge | Proposed | 2026-08-15 | Harness revision and run evidence ingestion into the Inspector normalization chain |
ADR-0004 |
Harness Checkpoint Experiment Compare | Proposed | 2026-08-17 | Checkpoint-anchored mixed-origin experiments, derived treatment axes, per-contrast verdicts, and the Studio experiment lifecycle |
ADR-0005 |
Checkpoint-backed Compare Sources and Materialization | Proposed | 2026-08-17 | Source-neutral checkpoint discovery, request provenance, adapter projections, and per-lane materialization |
ADR-0006 |
Session Notebook Trace and Outcome Projection | Proposed | 2026-08-18 | Ordered Turn evidence, response availability, evidence-bounded outcomes, and session-scoped patch requirements |
ADR-0007 |
Harness Studio Artifact Runtime and Provider Architecture | Proposed | 2026-08-22 | Revision-bound data and code lifecycles, renderer surfaces, external providers, and retained trace boundaries |
- Proposed: complete enough for architecture review, but not yet an accepted repository rule.
- Accepted: explicitly approved after the ADR's validation gate passes.
- Superseded: replaced by another named ADR; historical context and links remain available.
- Deprecated: retained for context but no longer governs new work.
Implementation does not happen merely because an ADR is Accepted. Non-trivial
implementation slices still require the dated Spec, acceptance scenarios, test
evidence, risk review, and activation gates required by AGENTS.md.