Architecture Decision Records (ADRs)¶
Compact records of significant design choices. Full rationale lives in DESIGN.md; each ADR captures the decision, consequences, and references.
Index¶
| ADR | Title | Status |
|---|---|---|
| ADR-001 | Provider registry (AWS / Azure / mock) | Accepted |
| ADR-002 | Dual RAG engines: chain vs langgraph |
Accepted |
| ADR-003 | Opt-in web research | Accepted |
| ADR-004 | RAGAS eval gating policy | Accepted |
| ADR-005 | Bounded helpdesk agent (LangGraph) | Accepted (mixed implementation — see ADR-006) |
| ADR-006 | Live LLM supervisor migration (supersedes unbuilt portions of ADR-005) | Proposed |
| ADR-007 | Agent capability registry and live campus router | Proposed |
Template¶
New ADRs should follow this shape:
# ADR-NNN: Title
**Status:** Proposed | Accepted | Superseded
**Date:** YYYY-MM-DD
## Context
What problem or constraint drove the decision?
## Decision
What we chose.
## Consequences
Positive and negative outcomes.
## Alternatives considered
What we did not choose and why.
## References
Links to code and docs.