Architecture Decision Records¶
This directory contains Architecture Decision Records (ADRs) for the HoloConf project.
What is an ADR?¶
An ADR is a document that captures an important architectural decision made along with its context and consequences. ADRs help us:
- Document the reasoning behind decisions
- Provide context for future developers
- Track the evolution of the architecture
- Enable informed discussions about changes
ADR Status¶
- Proposed - Under discussion, not yet accepted
- Accepted - Approved and in effect
- Superseded - Replaced by a newer ADR
- Deprecated - No longer relevant
Architecture Decisions¶
| ADR | Title | Status |
|---|---|---|
| ADR-001 | Multi-Language Architecture | Accepted |
| ADR-002 | Resolver Architecture | Accepted |
| ADR-003 | Async Execution Model | Accepted |
| ADR-004 | Config Merging Semantics | Accepted |
| ADR-005 | Resolver Timing (Lazy Resolution) | Accepted |
| ADR-006 | Repository and Package Structure | Accepted |
| ADR-007 | Schema and Validation | Accepted |
| ADR-008 | Error Handling Strategy | Accepted |
| ADR-009 | Serialization and Export | Accepted |
| ADR-010 | Thread Safety and Concurrency | Accepted |
| ADR-011 | Interpolation Syntax | Accepted |
| ADR-012 | Type Coercion | Accepted |
| ADR-013 | Testing Architecture | Accepted |
| ADR-014 | Code Quality Tooling | Accepted |
| ADR-015 | Documentation Site | Accepted |
| ADR-016 | PyO3 API Documentation | Accepted |
| ADR-017 | Release Process | Accepted |
| ADR-018 | Pull Request and Merge Process | Accepted |
| ADR-019 | Resolver Extension Packages | Accepted |
Creating a New ADR¶
- Copy
template.mdtoADR-NNN-short-title.md - Fill in all sections
- Submit for review
- Update this index
Template¶
See template.md for the ADR template.