This document is the index and governance entrypoint for Architectural Decision Records (ADRs). An ADR records a durable architectural choice, its context, rationale, consequences, and status.
Product direction, scope, priorities, roadmaps, and their rationale are
product-management decisions and belong in project memory, not in ADRs. An ADR
must not be used to turn a product preference or roadmap item into an
architectural contract. Architecturally Significant Requirements are recorded
in ASR.md; an ASR states what the architecture must satisfy, while
an ADR records why an architectural choice was made.
Future records use:
docs/adr/ADR-NNN-<slug>.md
NNN is a zero-padded, immutable sequence number. A record has one of these
statuses:
- Proposed — under review; not an accepted architectural commitment.
- Accepted — approved and currently authoritative.
- Superseded — replaced by a later ADR; retained for history.
Accepted ADRs should identify affected ASRs and the relevant overview or
implementation evidence. Superseding an ADR requires a link from the older
record to its replacement. Product-management decisions remain in the
tfmx project-memory decisions collection.
- ADR-001 — New Engine Not Line-by-Line Legacy Port — Accepted, 2026-08-15.
- ADR-002 — Private SDL-Free Playback Evidence Seam — Accepted, 2026-08-16.
- ADR-003 — Private Seam Placement — Accepted, 2026-08-17.
- ADR-004 — Tests Mirror Source Architecture — Accepted, 2026-08-16.
- ADR-005 — Target DAW Component Foundation — Accepted, 2026-08-19.
- ADR-006 — Private Header Co-location and Include Retirement — Accepted, 2026-08-19.
- ADR-007 — Audio Frame Block Boundary and Fixed First Format — Superseded by ADR-008, 2026-08-20.
- ADR-008 — Audio Frame Block Mixed-Value Boundary — Accepted, 2026-08-22.
- ADR-009 — Callback-Driven Audio Rendering — Accepted, 2026-08-22.
- ADR-010 — Native Adapter Ownership and Private Demand Coordination — Accepted, 2026-08-23.
ARCHITECTURE.md— concise current-system overview and architecture entrypoint.ASR.md— architecturally significant requirement register.AUDIO_RENDERING_DESIGN.md— callback-driven audio rendering design direction.VISION.md— product intent and future direction.../MEMORY.md— product-management decisions and roadmap context.