Architecture Decision Records¶

Architecture Decision Records capture project decisions that should remain easy to find after the implementation details move on.

ADRs are short. They record context, decision, consequences, and related issues or docs. They do not replace user documentation or implementation tasks.

Records¶

• 0001 - Release policy
• 0002 - Documentation layout
• 0003 - Supported platforms
• 0004 - API stability boundaries

Template¶

# NNNN - Title

Status: Proposed | Accepted | Superseded

## Context

What problem or constraint forced the decision?

## Decision

What did we choose?

## Consequences

What becomes easier, harder, or intentionally out of scope?

## Related

- Issue or documentation links.