An ADR records one decision that shapes the code, with its context and consequences, in a page or less. AGENTS.md holds the binding rules; an ADR records why a rule exists. Write one when a decision would otherwise be re-argued. Supersede an ADR with a new one rather than editing its decision.
ADRs are numbered in order: NNNN-short-slug.md.
# NNNN. Title
Status: Accepted | Superseded by NNNN
Date: YYYY-MM-DD
## Context
## Decision
## Consequences| # | Decision | Status |
|---|---|---|
| 0001 | Environment-only configuration | Accepted |
| 0002 | SQLite with Goose and sqlc for control state | Accepted |
| 0003 | Pinned DuckDB engine and batch format 4 | Accepted |
| 0004 | No legacy paths | Accepted |
| 0005 | CalVer releases | Accepted |
| 0006 | One structured query path | Accepted |
| 0007 | A hand-written PitotQL parser | Accepted |
| 0008 | Batch format 5 | Accepted |
| 0009 | Ingest admission at saturation | Accepted |