Development record
The docs chapter has the spec close refuse without a saved docs review for HEAD, but the build chapter's unattended landing runs that close with no stage that records one
The docs chapter has the spec close refuse without a saved docs review for HEAD, but the build chapter's unattended landing runs that close with no stage that records one
A sequencing impossibility (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/10-docs.md:92— "The spec close runs it over the intents the close would ship, before anything moves" - End B:
.abcd/development/brief/04-surfaces/34-build.md:743— "In the lane's worktree it runs the spec's close (which ships the intent"
10-docs says the doc-fidelity gate runs at the spec close over the intents it would ship, and a missing receipt for HEAD refuses with 'run the docs review first'. 34-build's landing runs the spec close in the lane's worktree to ship the intent, but its lane stages (worktree, brief, implementer, validators: ruthless, security, intent-auditor; landing) never run a docs review or record a docs-fidelity receipt for the lane's head. In a repository where the gate is armed, every spec-closing landing would be refused, so the loop as written cannot deliver an intent unattended.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 563.
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-2610262035195318 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262035195318-the-docs-chapter-has-the-spec-close.md
open on GitHub ↗ · commit history ↗
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.