Architecture Decision Records (ADRs)
This directory contains Architecture Decision Records (ADRs) documenting significant architectural decisions made in the Aragora project.
Index
| ADR | Title | Status | Date |
|---|---|---|---|
| 001 | Phase-Based Debate Execution | Accepted | Jan 2026 |
| 002 | Agent Fallback via OpenRouter | Accepted | Jan 2026 |
| 003 | Multi-Tier Memory System | Accepted | Jan 2026 |
| 004 | Incremental Type Safety Migration | Accepted | Jan 2026 |
| 005 | Composition Over Inheritance for APIs | Accepted | Jan 2026 |
| 006 | API Versioning Strategy | Accepted | Jan 2026 |
| 007 | Selection Plugin Architecture | Accepted | Jan 2026 |
| 008 | RLM Semantic Compression | Accepted | Jan 2026 |
| 009 | Control Plane Architecture | Accepted | Jan 2026 |
| 010 | Debate Orchestration Pattern | Accepted | Jan 2026 |
| 011 | Multi-Tier Memory Comparison | Accepted | Jan 2026 |
| 012 | Agent Fallback Strategy | Accepted | Jan 2026 |
| 013 | Workflow DAG Design | Accepted | Jan 2026 |
| 014 | Knowledge Mound Architecture | Accepted | Jan 2026 |
| 015 | Lazy Import Patterns | Accepted | Jan 2026 |
ADR Format
Each ADR follows this template:
# ADR-NNN: Title
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
What is the issue that we're seeing that is motivating this decision?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?
Contributing
When making significant architectural changes:
- Create a new ADR with the next available number
- Follow the template format
- Link related ADRs if applicable
- Update this README index