Architecture Decision Records (ADRs)¶
We document significant design decisions using lightweight ADRs. Each decision gets its own numbered file with context, options considered, and rationale.
Index¶
| # | Decision | Date | Status |
|---|---|---|---|
| 001 | AGPL-3.0 dual licensing | 2026-03-14 | Accepted |
| 002 | Release branch strategy | 2026-03-14 | Accepted |
| 003 | DuckDB for citation graph | 2026-03-14 | Accepted |
| 004 | No built-in LLM calls | 2026-03-14 | Accepted |
| 005 | SQLite response cache | 2026-03-14 | Accepted |
| 006 | Multi-source federation | 2026-03-14 | Accepted |
| 007 | Bipartite matrix pattern for networks | 2026-03-14 | Accepted |
| 008 | Input validation and security | 2026-03-15 | Accepted |
| 009 | Spatial visualization architecture | 2026-03-15 | Draft |
Format¶
Each ADR follows this structure:
# ADR-NNN: Title
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Superseded by ADR-NNN
## Context
What is the issue? What forces are at play?
## Options Considered
What alternatives were evaluated?
## Decision
What was chosen?
## Rationale
Why this option over the others?
## Consequences
What are the implications?