Architecture Decision Records (adr.github.io)

Maintain a decision log of architecturally significant choices using formats from adr.github.io.

When to use

• User asks for an ADR, architecture decision record, or decision log
• Before or during implementation — design fork, trade-off, or “which approach?” (decision checkpoints)
• User asks for key design decisions when doing work (checkpoint brief, not silent defaults)
• Recording a significant design choice (stack, integration, security, data model, deployment)
• Updating ADR status (accepted, deprecated, superseded)
• Aligning an existing repo with MADR / Nygard conventions

Decision checkpoints (layer 0)

Layer 0 = checkpoint (brief or proposed ADR). Layer 1 = accepted ADR after agreement.

When triggers fire, stop and ask—do not implement the most convenient option.