Development record
itd-86 defines the cold reading as one target document read against its own constraints; the reading chapter's detection position reads the shipped tree against the claim record, assembled at a commit from an include table.
itd-86 defines the cold reading as one target document read against its own constraints; the reading chapter's detection position reads the shipped tree against the claim record, assembled at a commit from an include table.
A premise contradiction (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/23-reading.md:193— "Where is the shipped tree in tension with the claim record?" - 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."
In 23-reading, the detection agent answers where the shipped tree is in tension with the claim record. Assembly takes only a position and a commit, and the reader gets what the committed include table admits. itd-86 instead scopes the cold reading as a surface that takes exactly one target document and detects only against constraints visible in that document. It also lands detections in the issue tier, while the chapter keeps reading records in the readings store, separate from the issue ledger. The two give incompatible objects for the same reading.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 634.
Deferral 2026-10-27
Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.
Frontmatter
| id | iss-2610262036146367 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262036146367-itd-86-defines-the-cold-reading-as-one.md
open on GitHub ↗ · commit history ↗
References1
- itd-86abcd Can Read Its Own Design Documents As A Stranger Wouldrelated
mentions3
- dcn-26102711123302352026-10-27 — The product thinker ruled on 2026-10-27 that the design brief shows the target design, in the present tense, with a status tag where a part is built, rather than the shipped state. With the ruling that behaviour lives in the command pages, the brief holds the product as aimed for and why, and the command pages hold what abcd does today. This reverses itd-147's currency rule, so a superseding ADR is owed, and the brief's checks are rebuilt around the status overlay.
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- dcn-26102711123395162026-10-27 — The product thinker ruled on 2026-10-27 that each abcd command's behaviour is written once, in its command page, which agents follow when they run it. The brief's chapter for the command keeps why the command exists, its trade-offs and why it refuses what it does, with its sub-verb table and generated appendix, and points to the command page for behaviour. The documentation-fidelity check moves to the command pages. This reverses the behaviour half of adr-2609231028044006 and invariant 18, so a superseding ADR is owed.