Architecture Decision
Use this when
A meaningful implementation choice affects interfaces, data, security, operations, compatibility, or future work.
Process
- Inspect the existing system and state the user or operational outcome being protected.
- Record constraints, known facts, assumptions, and non-goals.
- Describe two or three realistic options, including keeping the current design.
- Compare complexity, reversibility, compatibility, security, performance, and maintenance cost.
- Choose the smallest option that satisfies the outcome and explain why.
- Define consequences, migration or rollback needs, and a date or condition for revisiting the choice.
Output
Use: Status, Context, Decision, Alternatives, Consequences, Verification, and Follow-up.
Guardrails
Do not invent system constraints. Do not use an architecture record to hide an unresolved product decision or to justify unnecessary infrastructure.
1---2name: architecture-decision3description: Record a focused technical decision with context, alternatives, tradeoffs, and follow-up.4---56# Architecture Decision78## Use this when910A meaningful implementation choice affects interfaces, data, security, operations, compatibility, or future work.1112## Process13141. Inspect the existing system and state the user or operational outcome being protected.152. Record constraints, known facts, assumptions, and non-goals.163. Describe two or three realistic options, including keeping the current design.174. Compare complexity, reversibility, compatibility, security, performance, and maintenance cost.185. Choose the smallest option that satisfies the outcome and explain why.196. Define consequences, migration or rollback needs, and a date or condition for revisiting the choice.2021## Output2223Use: Status, Context, Decision, Alternatives, Consequences, Verification, and Follow-up.2425## Guardrails2627Do not invent system constraints. Do not use an architecture record to hide an unresolved product decision or to justify unnecessary infrastructure.
milind-soni