Architecture Decision Records (ADRs)¶
This section contains Architecture Decision Records (ADRs) for the amiable-templates project. ADRs document significant architectural decisions, their context, and consequences.
What is an ADR?¶
An Architecture Decision Record captures an important architectural decision along with its context and consequences. We use ADRs to:
- Document why decisions were made
- Provide context for future contributors
- Enable informed decision-making about changes
- Track the evolution of the project
ADR Process¶
- Draft: Create an ADR using the template
- Review: Submit for LLM Council review (optional but recommended)
- Propose: Open a PR for community feedback
- Accept/Reject: Core team makes final decision
Current ADRs¶
| ADR | Title | Status | Date |
|---|---|---|---|
| ADR-000 | Template | N/A | - |
| ADR-001 | Project Structure & OSS Standards | Accepted | 2026-01-03 |
| ADR-002 | MkDocs Site Architecture | Accepted | 2026-01-03 |
| ADR-003 | Template Configuration System | Accepted | 2026-01-03 |
| ADR-004 | CI/CD & Deployment | Accepted | 2026-01-03 |
| ADR-005 | DevSecOps Implementation | Accepted | 2026-01-03 |
| ADR-006 | Cross-Project Documentation Aggregation | Accepted | 2026-01-03 |
LLM Council Reviews¶
ADRs in this project are reviewed by the LLM Council for architectural feedback. The council provides:
- Multi-model perspectives on design decisions
- Identification of risks and gaps
- Suggestions for alternatives
- Consensus-driven recommendations
Council review tiers: - Quick: 2 models, ~10 seconds - Balanced: 3 models, ~25 seconds - High: Full council, ~45 seconds