--- status: proposed date: YYYY-MM-DD decision-makers: [names or roles] # consulted: [subject-matter experts with two-way communication] # informed: [stakeholders kept up-to-date with one-way communication] --- # NNNN. {short title, representative of solved problem and found solution} ## Context and Problem Statement {Describe the context and problem statement in two to three sentences, or as a short illustrative story. Articulate the problem as a question if helpful, and link to issues, PRs, or discussions.} ## Decision Drivers - {decision driver 1, e.g., a force, facing concern, quality attribute} - {decision driver 2} - … ## Considered Options - {title of option 1} - {title of option 2} - {title of option 3} - … ## Decision Outcome Chosen option: **"{title of option X}"**, because {justification — e.g., the only option meeting a k.o. criterion, resolves driver {driver}, or comes out best in the comparison below}. ### Consequences - Good, because {positive consequence}. - Bad, because {negative consequence / accepted trade-off}. - Follow-up: {action item, if any}. ### Confirmation {How will compliance with this ADR be confirmed? E.g., a design/code review, an ArchUnit test, a CI check, or a follow-up audit.} ## Pros and Cons of the Options ### Comparison | Driver | {Option 1} | {Option 2} | {Option 3} | | ---------- | ---------- | ---------- | ---------- | | {driver 1} | Yes | Maybe | No | | {driver 2} | No | Yes | Yes | ### {title of option 1} {example | description | pointer to more information} - Good, because {argument}. - Neutral, because {argument}. - Bad, because {argument}. ### {title of option 2} {example | description | pointer to more information} - Good, because {argument}. - Bad, because {argument}. ## More Information {Additional evidence/confidence for the decision, team agreement notes, when/how to revisit, links to related ADRs and resources.}