Development record
itd-87 escalates a finding that matches a resolved or wontfixed record as a new entry; the consistency pass marks such a finding addressed and files nothing
itd-87 escalates a finding that matches a resolved or wontfixed record as a new entry; the consistency pass marks such a finding addressed and files nothing
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-87-recurrence-escalation-in-capture.md:17— "the ledger no longer quietly folds it into the closed entry. It escalates: a new entry, citing the closed one" - End B:
.abcd/development/intents/planned/itd-2609291923559186-the-consistency-pass-runs-where-records.md:87— "fix is markedaddressedon the report, naming the record, and files"
itd-87 says a finding that matches an entry already resolved or wontfixed must not be folded into the closed entry: it becomes a new entry citing the closed one, because the recurrence is evidence that the closure may be wrong. itd-2609291923559186 G1 says that when a consistency finding's record is already resolved or won't-fix, the report marks it addressed and files nothing. The two give opposite rules for the same event in the issue ledger.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1184.
Frontmatter
| id | iss-2610262044079779 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262044079779-itd-87-escalates-a-finding-that-matches.md
open on GitHub ↗ · commit history ↗
References2
- itd-87A Finding That Comes Back After You Closed It Tells You Something, And abcd Stops Throwing It Awayrelated
- itd-2609291923559186The consistency pass runs where records are written and names each finding the same way every timerelated