Architecture Decision Records (ADR)
This directory stores architecture decisions that have lasting impact on project structure, behavior, or contribution workflow.
Purpose
Use ADRs to capture:
- Decision context
- Chosen option
- Alternatives considered
- Consequences and follow-ups
ADRs avoid re-litigating the same design decisions and provide maintainers with historical rationale.
Status Values
Use one status per ADR:
- Proposed
- Accepted
- Superseded
- Rejected
- Deprecated
Naming Convention
File pattern:
NNNN-short-kebab-case-title.md
Examples:
0001-facade-overrides-platform-registrations.md0002-broadcasting-factory-consistency-strategy.md
Required Sections
Each ADR should include:
- Title
- Status
- Date
- Context
- Decision
- Alternatives Considered
- Consequences
- Follow-up Actions
ADR Index
- 0000 - Template
- 0001 - Facade Registrations Override Platform Interface Bindings
- 0002 - Broadcasting Factory Consistency Strategy
When adding new ADRs, append them to this index.