Architecture Decision Records

An ADR here records a substantial, load-bearing architecture decision: the context that forced it, the options weighed, the choice made, and its consequences. That’s a different bar than Decisions, which logs smaller pre-1.0 calls (SDK floors, version pins, docs stack) as short decision/rationale/trigger entries. An ADR gets a number, a full context/options/decision/consequences writeup, and a verification plan; a decisions.md entry gets a paragraph.

Status reflects the current codebase, not the date the ADR was written. Some of these describe features that are fully built and shipping; ADR 0004 describes a design that has not been implemented yet — read its status line before treating anything in it as current behavior.

Numbering note: two ADRs share the number 0003 (0003-embeddable-components and 0003-contracts-first-internals) — a pre-existing collision from when the latter was written, not introduced here. Both are listed below by their full slug; treat the number as non-unique and always link by slug, not by number alone.

ADR	Title	Status
0001	Cross-target trace correlation	Implemented
0002	Production capture for a debug cohort	Implemented
0003	Embeddable components (P5 founding ADR)	Implemented
0003	Contracts-first internals, plugins on the open axes	Accepted — first contract shipped
0004	Remote debug sessions	Proposed — not yet built
0005	Package consolidation and naming	Implemented
0006	CaptureSource, the first contract off ADR 0003	Accepted — 2 of 9 sources migrated
0007	Ship on Solid 2.0 at the RC	Implemented