Skip to content

[Short noun phrase naming the decision]

Context

[Describe the problem and the forces at play (technical, organizational, regulatory, etc.) that motivate this decision. Plain prose, 2-4 paragraphs. Authors MUST cite the underlying constraint or driver.]

Decision Drivers

[Bulleted list of the constraints, goals, and qualities that this decision MUST optimize for. Each driver SHOULD be testable.]

  • [driver-1]
  • [driver-2]
  • [driver-3]

Considered Options

[List at least two options. The author MUST include the eventually-selected option. Each option gets a short subsection below with Pros/Cons.]

  • [option-1]
  • [option-2]
  • [option-3]

Decision Outcome

Chosen option: "[option-name]", because [justification — cite the decision driver(s) it best satisfies].

Positive Consequences

  • [consequence-1]
  • [consequence-2]

Negative Consequences

  • [consequence-1]
  • [consequence-2]

Consequences

[A paragraph describing the post-decision world. What changes for engineers, operators, users? What follow-up work is implied? What review cadence applies?]

Pros and Cons of the Options

[option-1]

[1-2 sentences describing the option.]

  • Good, because [argument-a]
  • Good, because [argument-b]
  • Bad, because [argument-c]

[option-2]

[1-2 sentences describing the option.]

  • Good, because [argument-a]
  • Bad, because [argument-b]
  • Bad, because [argument-c]
  • [Optional: link to related ADRs, RFCs, or external references.]