Development record
itd-86, still a draft, promises cold-reading detections that land as reading records; the capture chapter says the reading producer has shipped and owns that output contract.
itd-86, still a draft, promises cold-reading detections that land as reading records; the capture chapter says the reading producer has shipped and owns that output contract.
A scope leakage (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-86-cold-reading-surface.md:35— "Each detection lands as a reading record in the issue tier via the cold-reading output contract" - End B:
.abcd/development/brief/04-surfaces/06-capture.md:610— "this surface and it ships: the reading verb's ingest owns the output contract"
itd-86 still lists as undelivered that each detection lands as a reading record in the issue tier through the cold-reading output contract. 06-capture.md says the producer of reading items has shipped and that the reading verb's ingest owns the output contract. A shipped surface and an open draft claim the same ground.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 495.
Frontmatter
| id | iss-2610262034268156 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262034268156-itd-86-still-a-draft-promises.md
open on GitHub ↗ · commit history ↗
References1
- itd-86abcd Can Read Its Own Design Documents As A Stranger Wouldrelated