One file per decision, most within a page — 005, 010 and 011 run to about two once their Revisited sections are counted — with the options that were considered and rejected. Several were reversed by measurement; those carry a Revisited or Superseded section rather than being edited to look like they were right the first time.
| # | Decision | Status |
|---|---|---|
| 001 | LangGraph for control flow, direct API calls inside nodes | accepted |
| 002 | No Temporal for v1 | accepted, revisit trigger fired |
| 003 | Cohere as actor, a different model family as judge | accepted, amended twice |
| 004 | arXiv + Semantic Scholar, no PDF parsing | superseded by 011 |
| 005 | Public deployment, demo mode, budget cap | deferred, then reversed: fence built, deploy not |
| 006 | Langfuse for tracing, Redis for an LLM cache | accepted, amended |
| 007 | The switch is the UI | accepted, revisited (one page became six routes) |
| 008 | Hybrid retrieval in Postgres, not Elasticsearch | accepted, amended (two-stage adopted on the agent path) |
| 009 | Hand-rolled chunking, not a chunking library | accepted, revisited |
| 010 | Grounding is lexical, not embedding similarity | accepted, corrected |
| 011 | Full text via arXiv/ar5iv HTML, not PDF | accepted, supersedes 004 |
| 012 | Retrieval becomes a tool the agent chooses; chunks stay | accepted |
| 013 | Local models: judge and embeddings now, actor deferred | accepted |
The three worth reading if you read three. 010 — a measurement showed embedding similarity cannot detect a swapped figure, and a later one showed the conclusion drawn from it about the lexical checker was itself caused by a bug in that checker. 008 — a retrieval metric improved while answers got worse, which is how you ship a regression with a rising graph. 005 — the decision that reversed twice: deployment was planned on day 1, dropped on day 13 over an unfenced public endpoint, and the fence that objection named was built on day 14. The deployment itself is still not done, so the ADR records a reversal whose conclusion has not yet been acted on.