Architecture decision records¶

Each record captures one decision: the context that forced it, the options considered, and the consequences we accepted. Records are immutable once accepted; a changed decision gets a new record that amends or supersedes the old one. Proposals that precede decisions live in ../rfcs/.

ADR	Title	Status
0001	Typed verdicts over any Pydantic model	Accepted
0002	DSPy judges and decision models as equals	Accepted
0003	Datasets and experiments in Langfuse and Hugging Face	Accepted
0004	Trunk-based development with RFCs, ADRs and evergreen docs	Accepted
0005	Quality gates and license	Accepted
0006	Ports and adapters	Accepted, amended by 0011
0007	Trained judges saved as JSON files	Accepted
0008	Decision-only views, and hand-off by composition	Accepted
0009	Online evaluation: sampling by key, soft budgets, and events as log records	Accepted
0010	The documentation site, and publishing it from main	Accepted, amended by 0013
0011	Scores shared with the libraries	Accepted, partly superseded by 0012
0012	Langfuse score adapters in evalr	Accepted
0013	Docstrings in Markdown, and one docs build	Accepted

To add a record, copy template.md to the next number and add a row above.