Development record
eight pruned ADR ids are still cited by later records, and for four of them (adr-4, adr-8, adr-16, adr-18) the citations are live by-name references that the decisions charter's retention clause says keep a record restorable: either restore those four from the pruning commits as status superseded records, or record a maintainer ruling that body-prose citations do not count as cite for the retention clause. Needs the maintainer's call — the two remedies diverge and neither is obviously right.
issueopenminoriss-2608271804496010
eight pruned ADR ids are still cited by later records, and for four of them (adr-4, adr-8, adr-16, adr-18) the citations are live by-name references that the decisions charter's retention clause says keep a record restorable: either restore those four from the pruning commits as status superseded records, or record a maintainer ruling that body-prose citations do not count as cite for the retention clause. Needs the maintainer's call — the two remedies diverge and neither is obviously right.
Remedy grounds (2026-09-29)
- The charter's retention sentence (a superseded ADR is pruned unless later records still cite it) is the rule both branches must satisfy, so each remedy edits either the records or that sentence and nothing else.
- No outside-practice check: the question is this repository's own retention clause.
- Rejected: rewriting the citing records to drop the names, which erases the trail the retention clause protects.
Frontmatter
| id | iss-2608271804496010 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2608271804496010-four-pruned-adrs-are-still-cited-by-name.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-2609151138388536Every Decision Is Its Own Record, and the Log Stops Conflicting