Skip to content

ADRs

Architecture decision records (ADRs): context, options considered, the decision, and its consequences. Distinct from the CHANGELOG's "what changed" — this is "why."

Current ADRs: none. The prior corpus (six ADRs, numbered sequentially in docs/decisions/) was retired on 2026-08-28 — they predated the ENG-02 Foundation/ADR workflow and shouldn't be read as decisions produced under that approved process. Their history lives in the CHANGELOG instead. This section is ready for the next ADR produced through that workflow; there isn't one yet.

The Decision Register, Immediate Open Decisions, and Build vs. Buy pages alongside this one sit in the same "Decisions & Architecture Governance" group but are different things:

  • Decision Register — a lightweight coordination/visibility tracker for open, proposed, decided, and deferred cross-cutting questions (ENG-02 §15, ENG02-25), generated from the owning development repository's canonical data and retaining every item permanently. It is never authoritative and never replaces an ADR — a DECIDED item there points back to the real decision (an ADR here, or another authoritative source), it doesn't stand in for one.
  • Immediate Open Decisions — the same canonical register data, filtered to unresolved items (status OPEN or PROPOSED) that also need near-term attention (needed_imminently: true). Not a separate record — same data, narrower slice.
  • Build vs. Buy — recommendation/input material for decisions not yet made, not authoritative decision state.