Blame
|
1 | # Template — Architecture Decision Record |
||||||
| 2 | ||||||||
| 3 | **Status:** Proposed / Accepted / Superseded / Rejected |
|||||||
| 4 | **Date:** YYYY-MM-DD |
|||||||
| 5 | **Decision owners:** |
|||||||
| 6 | ||||||||
| 7 | ## Context |
|||||||
| 8 | ||||||||
| 9 | What problem, constraint or repeated ambiguity requires a durable decision? |
|||||||
| 10 | ||||||||
| 11 | ## Decision |
|||||||
| 12 | ||||||||
| 13 | State the chosen approach precisely. |
|||||||
| 14 | ||||||||
| 15 | ## Alternatives considered |
|||||||
| 16 | ||||||||
| 17 | Describe credible alternatives and why they were not selected. |
|||||||
| 18 | ||||||||
| 19 | ## Consequences |
|||||||
| 20 | ||||||||
| 21 | Record benefits, trade-offs, compatibility implications, migration cost and operational effects. |
|||||||
| 22 | ||||||||
| 23 | ## Follow-up |
|||||||
| 24 | ||||||||
| 25 | Implementation tasks, tests, migration work and documentation that must change. |
|||||||
| 26 | ||||||||
| 27 | ## Supersession |
|||||||
| 28 | ||||||||
| 29 | If this ADR replaces or is replaced by another ADR, link both directions. |
|||||||