Decision tags — What a decision is about, in the order the index shows them. Open, unlike the topics: a decision that needs a word it does not have simply gets one.
Migration — moving off the YAML registry, and what happens to it.
4 of 66 decisions. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| ADR-001 | Keep the anthology in a Luria record rather than in YAML the build reads | The YAML already modelled a knowledge record — statuses, supersession, an attic, a topic taxonomy — but nothing checked any of it, and three of the four were provably inert. Adopting Luria keeps the model and attaches the checks. Rejected: writing bespoke validators against the existing schema, which is the same work without the generated views or the citation graph. | Active |
| ADR-006 | Generate the registry from the record instead of checking it in | registry.yaml and REGISTRY.md are already derived from research.yaml and committed as though they were sources. Once the record is ground truth they should be built from it as artifacts for the frontend. Proposed, not Active: the inversion is phase 4 and the frontend contract has not been checked yet. | Superseded — by ADR-008; by ADR-008, which retires the pipeline rather than inverting it |
| ADR-008 | Retire the registry pipeline and publish the record itself | ADR-006 proposed generating registry.yaml from the record so the frontend could keep consuming it. Publishing the record directly is simpler and removes the projection rather than inverting it: luria stages the record as a site, so the registry builder, REGISTRY.md and the bespoke frontend all retire together. Supersedes ADR-006. | Active |
| ADR-033 | Readings made in another context port into the record; their agenda does not | Seventy-four paper notes arrived from a separate project on decentralized training. They are this record’s own readings, made under a different agenda, and their schema turns out to be the NOTE schema — the same twelve fields in the same order. So they port: 70 NOTE documents and 67 new LIT notes. What does not port is decided by scope rather than by trust — one field answers another project’s five questions, 17 recommendations name that project’s own system, and 6 are advice on proof technique. Metadata comes from arXiv and CrossRef in every case, because three readings were bound to the wrong identifier and one citation was invented outright. | Active |