Title¶
A brief, concise name for the architectural decision
Status¶
Proposed | Accepted | Deprecated | Superseded by ADR-xxx
Date¶
YYYY-MM-DD
Context¶
Describe the problem or situation that necessitates a decision. Specify constraints, business priorities, and technical or team-specific factors. Provide the necessary background so that the rationale behind the decision is clear.
Decision¶
State the chosen decision clearly and unambiguously. Use affirmative language, for example: “PostgreSQL will be used as the primary database.” Be concise and stay on point.
Consequences¶
Positive¶
List the key benefits and improvements expected from this decision.
Negative¶
Note potential drawbacks, risks, or costs associated with this decision. Mitigation:
Include any follow-up tasks or impacts on other decisions. Mitigation:
Alternatives¶
Briefly describe other options that were considered and why they were rejected.
References¶
Links to supporting documents, discussions, patterns, or research that influenced the decision.
Participants¶
List of personnel who participated in the decision.
Name1
...