itd-82 says a record filed before the remedy rule has no remedy and is ineligible; 35-drain reads such a record's legacy suggested_fix as its remedy

itd-82 says a record filed before the remedy rule has no remedy and is ineligible; 35-drain reads such a record's legacy suggested_fix as its remedy

A terminology drift (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/planned/itd-82-drain-ledger-triage.md:44 — "a record filed before the rule carries none, and is ineligible and listed as such"
• End B: .abcd/development/brief/04-surfaces/35-drain.md:75 — "record written before the field existed reads its suggested_fix: as its remedy."

In itd-82 a remedy is only the remedy: field, so a record filed before the rule carries none and is ineligible and listed as such until a person adds one. 35-drain uses remedy in a wider sense: a record written before the field existed has its suggested_fix: read as its remedy, so it can pass the remedy test and be drained. A builder cannot follow both for the older backlog. Under one reading those records are listed as ineligible, and under the other they are worked unattended.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 738.