Architecture Decision Records

ADRs help teams preserve the reasoning behind meaningful technical decisions.

Suggested template

# ADR: Decision title

## Status
Accepted

## Context
What problem are we solving?

## Decision
What did we choose?

## Consequences
What improves, what becomes harder, and what follow-up work exists?

When to create an ADR

• Choosing between competing architectural options
• Introducing a new platform capability
• Setting a pattern other teams may follow
• Making a decision that is hard to reverse later

Related sections

• System Design Patterns for the kinds of decisions worth capturing in ADRs.
• Engineering Principles for the decision-making standards behind those records.
• Code Review Guidelines for how architectural changes should be reviewed in pull requests.