Development record
The read-block entry puts all the instrument's own outputs inside the block, while invariant 15 admits widening-run items at the comparative position
The read-block entry puts all the instrument's own outputs inside the block, while invariant 15 admits widening-run items at the comparative position
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/ledger/read-block.md:17— "The instrument's own outputs, manifests and reading records, sit inside the read-block on the next run." - End B:
.abcd/development/brief/02-constraints/03-invariants.md:167— "The instrument's own output is never its input, with one positional exception adr-2609021016272867 states"
The glossary says the instrument's own outputs, manifests and reading records sit inside the read-block on the next run, with no exception. Invariant 15 says the instrument's own output is never its input with one positional exception: at the comparative position, two body fields of a derived widening run's items are admitted as the candidate set. An assembler built from the glossary excludes what the invariant requires the comparative reading to receive.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 160.
Frontmatter
| id | iss-2610262031401131 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031401131-the-read-block-entry-puts-all-the.md
open on GitHub ↗ · commit history ↗
mentions2
- adr-2609021016272867The comparative reading receives one widening run's candidates, a positional exception to the prior-run exhaust, with the run derived from the record and no operand added
- iss-2610262036018615The read-block glossary keeps every reading record of a prior run out of the next run; 23-reading hands the comparative reading a prior widening run's items.