Generated by luria index from the record’s frontmatter — built, not edited.
Proposed and Deferred both describe an open question. Neither says since when, and that is the signal: a decision proposed last week is pending; the same one a year later was either overdue or settled in code and never written back.
5 document(s) awaiting a decision.
ADRs
4 of the 5.
| Open since | Status | Code | Cited | Unack. | Title |
|---|---|---|---|---|---|
| 2026-10-07 | Proposed | ADR-127 | 9 | 9 | A logic core in clingo, behind a procedural shell |
| 2026-10-07 | Proposed | ADR-126 | 6 | 6 | A reference may name several schemes |
| 2026-10-08 | Proposed | ADR-128 | 0 | 0 | Configuration is the only source of relation semantics |
| 2026-10-13 | Proposed | ADR-129 | 5 | 5 | A chain may walk a named path pattern |
DPs
1 of the 5.
| Open since | Status | Code | Cited | Unack. | Title |
|---|---|---|---|---|---|
| 2026-09-29 | Proposed | DP-018 | 7 | 0 | Make mutable premises explicit dependencies |
The citation count is the second axis, and it flips the priority: an old proposal nothing references is a stalled idea worth closing, while an old proposal many files cite is a decision the codebase has already made and hasn’t written down.
This count and the reference-status report’s will differ, and that is not an off-by-one. That report covers documents something actually cites and hasn’t acknowledged; this one covers every undecided document. One here is missing from there for exactly one of two reasons: nothing cites it, or every citation carries an inactive-ok annotation.
Cited nowhere at all (1): ADR-128 — this is the cheapest to close, since nothing depends on the answer.