Warning
🚧 Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Architecture Decision Records (ADRs)
ADRs record significant architectural decisions: what was decided, why, and which alternatives were considered.
Why use ADRs?
With team turnover and an evolving system landscape, it’s common to lose context around technical decisions. ADRs create an organizational memory that answers the question: “why did we do it this way?”
How to create an ADR
- Copy the template:
standards/templates/template-adr.md - Name it
ADR-NNN-short-title.md(sequential numbering) - Fill in all fields
- Open a PR on GitHub for architecture team review
Recorded ADRs
| ID | Title | Status | Date |
|---|---|---|---|
| ADR-001 | Data lake on BigQuery (GCP) | ✅ Accepted | 2024 |
| ADR-002 | Authentication via Entra ID | ✅ Accepted | 2024 |
| ADR-003 | Documentation portal: MkDocs + Azure Static Web Apps | ✅ Accepted | 2025 |
Possible statuses
- Proposed — under discussion
- Accepted — decision made and in effect
- Deprecated — replaced by another ADR
- Superseded — replaced; reference the new ADR