principle-record-decisionslisted

# Record Decisions When a non-obvious decision settles, write it down as an ADR: the options considered, the pick, and why. Offer this proactively; do not wait to be asked. **Why:** The pick without the why re-litigates itself. Months later the rejected option looks fresh, nobody remembers what killed it, and the argument reruns from zero or the mistake reruns in code. A recorded rejection is recoverable: when the constraints change, the ADR says exactly which assumption to re-check. **Pattern:** - Trigger on decisions where a reasonable engineer could have picked differently: stack choices, swaps, integration approaches, experiment outcomes, design-space picks. - Record the options considered, the decision, and the reasons, including why each rejected option lost. The why is the payload. A decision log without reasons is a changelog. - Keep ADRs in the repo's decisions directory (`docs/decisions/` in this repository), numbered, one decision per file. - For prototype-driven decisions, the kept studies plus a short "chose B because" note are the ADR (the **exhaust-the-design-space** principle skill). - Do not record the obvious. A decision with one viable option is not an ADR; that entry is noise the next reader pays for.