Skip to content

ADR-0000:

  • Status: Proposed | Accepted | Deprecated | Superseded by ADR-NNNN
  • Date: YYYY-MM-DD
  • Deciders:
  • Tags: db, http, security>

Context

What problem are we solving? What forces are at play (technical, organizational, regulatory)? Cite constraints from principles.md §2 (Power of 10, SEI CERT, SLSA, etc.) where relevant.

Keep it short. One or two paragraphs. The reader should understand why a decision was needed, not the full history.

Decision

State the decision in active voice: "We will use X." One paragraph max.

Alternatives considered

Option Pros Cons Why not chosen
Option A … … …
Option B … … …

At minimum list the runner-up. If the alternatives section is empty, the decision wasn't real — it was a default.

Consequences

  • Positive: what becomes easier, faster, safer.
  • Negative: what becomes harder, slower, more expensive (operationally or cognitively).
  • Neutral / follow-ups: things that must happen because of this decision (new tests, docs, migration steps, deprecation timeline).

References

  • Upstream docs, RFCs, blog posts, prior ADRs.
  • Related issues / PRs: #NNN.