Development record
The recurrence draft says the ledger folds a match into the closed entry, but the shipped matcher always writes a new record and links it as a duplicate
The recurrence draft says the ledger folds a match into the closed entry, but the shipped matcher always writes a new record and links it as a duplicate
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" - End B:
.abcd/development/intents/shipped/itd-2609212137116617-a-new-capture-or-draft-is-matched.md:40— "a likely match is written onto the new record asduplicates:(near-identical) orrefines:(narrower), naming the candidate"
itd-87's premise is that today a finding matching a resolved or wontfixed entry is folded into the closed entry and its evidence destroyed. itd-2609212137116617 compares new text with open and resolved issues and writes a new record carrying a duplicates: or refines: link, never dropping anything. The draft describes current behaviour wrongly, and its recurrence-versus-duplicate distinction falls on the link vocabulary the shipped record defines.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1202.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262034242423. Same contradiction with the shipped matcher intent as the capture chapter version: the draft says the ledger folds a match away, the shipped matcher writes a new record with a duplicates: or refines: link.
Frontmatter
| id | iss-2610262044221992 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262044221992-the-recurrence-draft-says-the-ledger.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-2609212137116617A new capture or draft is matched against the record before it is writtenrelated
mentions2
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2610262034242423itd-87 says capture matching covers only open entries and folds recurrences away; the capture chapter says the match already covers resolved issues and never drops a capture.