Architecture Decision Record Generator
Fill the form and generate a concise Markdown Architecture Decision Record ready for a team or coding agent.
A report can be previewed, but without a target name it is not a shareable technical record.
# ADR: Architecture decision **Status:** Accepted **Date:** 2026-08-10 ## Context — ## Decision drivers — ## Options considered - — ## Decision — ## Consequences and trade-offs — ## Reversal / revisit condition — ## Evidence — ## Assumptions — ## Validation plan —
PDF / human · MD / repo · JSON / automation
Architecture Decision Record Generator
5 decision-evidence gaps
An ADR does not declare a decision correct; it makes context, alternatives, evidence, consequences and revisit conditions traceable.
Executive brief
Findings and decision points
Context missing
The decision can be recorded but should not be treated as strong until the evidence chain is complete.
Drivers missing
The decision can be recorded but should not be treated as strong until the evidence chain is complete.
Options missing
The decision can be recorded but should not be treated as strong until the evidence chain is complete.
Evidence missing
The decision can be recorded but should not be treated as strong until the evidence chain is complete.
Validation plan missing
The decision can be recorded but should not be treated as strong until the evidence chain is complete.
Evidence ledger
Method, assumptions and boundaries
- • No explicit assumption supplied.
- • ADR is not a benchmark or automatic architecture validation.
Recommended next move
The report is not sales decoration; it is a technical decision record.
Each report separates observations, user input, derived conclusions and heuristic assumptions. If evidence is weak, confidence drops.