Development record
Invariant 19 lists every record filed before the remedy field as ineligible, but the drain reads such a record's suggested_fix as its remedy
Invariant 19 lists every record filed before the remedy field as ineligible, but the drain reads such a record's suggested_fix as its remedy
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/02-constraints/03-invariants.md:175— "a record filed before that carries none and is listed as ineligible" - End B:
.abcd/development/brief/04-surfaces/35-drain.md:75— "record written before the field existed reads itssuggested_fix:as its remedy"
Invariant 19 states that a record filed before remedies were required carries none and is listed as ineligible. The drain chapter says such a record reads its suggested_fix: as its remedy, so a legacy record that has one can pass the remedy clause and be taken by a machine. The invariant's fixed disposition and the drain's fallback disagree about what happens to the same records.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 72.
Frontmatter
| id | iss-2610262031008610 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031008610-invariant-19-lists-every-record-filed.md
open on GitHub ↗ · commit history ↗