decision-recordlisted

# Writing a decision record *Carries out rules D1, D2, D3 and G2. The [catalogue](https://github.com/nanatsusaya/agent-driven-development/blob/main/method/rules.md) is the authority; this file is only the procedure.* Authoring a decision is a repeatable procedure. Follow it exactly: decisions are **normative** and everything built later rests on them. Keep it a *decision record*, never a shadow implementation. If a section is turning into a design document, the design belongs elsewhere and this file should say which choice was made and why the alternatives were not. **Guardrails (do not violate):** - **Do not answer the open questions yourself.** They exist because they belong to the decider. - **Do not edit an accepted decision.** See step 1. - **Do not implement what this decision is still deciding.** ## 0. Read the ground truth first - The state artefact — the current phase and what this decision is meant to unblock. - The decisions index — the statuses and the next free number. - The owning ticket, if there is one: its context, its scope, its criteria. - **Every accepted decision this one depends on or touches.** Actually read them; do not paraphrase from memory. - The operating-rules artefact, especially its stop-and-ask list. ## 1. Classify the change - **A new decision** → a new record at the next free number. Numbers are never reused. - **A change to an accepted decision** → **stop and ask.** An accepted decision is immutable except with explicit au