Architecture Decision Records¶
ADRs document significant technical decisions, their context, and reasoning. They help the team understand why a particular approach was chosen and what alternatives were considered.
Registry¶
| ID | Title | Date | Status |
|---|---|---|---|
| 0001 | Predictable ArgoCD behavior for stateful applications | 2026-02-26 | Accepted |
Creating a new ADR¶
File naming: NNNN-short-title.md (zero-padded sequential number)
Example: 0002-use-kraft-instead-of-zookeeper.md
Template¶
# ADR-NNNN: <Title>
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-XXXX
**Author:** Name
**JIRA:** [DEVOPSBLN-XXXX](https://tickets.digitalturbine.com/browse/DEVOPSBLN-XXXX)
## Context
What is the issue or situation that motivates this decision?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or harder as a result of this decision?
## Alternatives Considered
What other options were evaluated, and why were they rejected?
## Related documents
- [Runbook](../runbooks/YYYY-MM-DD_description.md)
- [Test Scenarios](../test-scenarios/YYYY-MM-DD_description.md)
Tip
Always cross-link the ADR to its runbook and test scenarios. Future readers need the full chain: why (ADR) -> how (runbook) -> proof (test scenario).