Development record
Invariant 15 refuses any path at a reading's invocation, but itd-86's cold reading takes exactly one target document.
Invariant 15 refuses any path at a reading's invocation, but itd-86's cold reading takes exactly one target document.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/02-constraints/03-invariants.md:167— "a repository path is never accepted at the invocation" - End B:
.abcd/development/intents/drafts/itd-86-cold-reading-surface.md:29— "A surface that takes exactly one target document and produces candidate detections against the constraints visible in that document alone."
Invariant 15 says a reading's operands are only a position and a target state, that what it is handed comes from the committed preset for that position, and that a repository path is never accepted at the invocation (adr-2609021016286571, which supersedes adr-58's scope operand). itd-86, still listed by invariant 14 as a consumer, defines the cold reading as a surface that takes exactly one target document.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 183.
Frontmatter
| id | iss-2610262031492489 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031492489-invariant-15-refuses-any-path-at-a.md
open on GitHub ↗ · commit history ↗
References1
- itd-86abcd Can Read Its Own Design Documents As A Stranger Wouldrelated
mentions2
- adr-58A reading is commissioned about something, so the invocation takes a scope
- adr-2609021016286571The invocation is a position and a target state, and the committed preset for the position supplies the rest