An ADR is a short document that captures one significant architectural decision: the context, the decision itself and its consequences. The format was popularised by Michael Nygard in 2011.
Code tells you what the system does. ADRs tell you why it looks the way it does.
# ADR-0007: Use PostgreSQL as primary database
- **Status:** Proposed | Accepted | Deprecated | Superseded by ADR-0012
- **Date:** 2026-10-23
- **Deciders:** names / roles
## Context
What problem are we solving? What forces are at play
(requirements, constraints, team skills, deadlines, costs)?
## Options considered
1. PostgreSQL
2. SQL Server
3. MongoDB
## Decision
We will use PostgreSQL because …
## Consequences
- ✅ Positive: …
- ⚠️ Negative / accepted risks: …
- 🔁 Follow-up work: …
docs/adr/) so they are reviewed in pull requests