Development record
itd-57 holds a spec back through a native spec dependency that the selector already honours; the native spec store shipped by itd-80 has no dependencies between specs
itd-57 holds a spec back through a native spec dependency that the selector already honours; the native spec store shipped by itd-80 has no dependencies between specs
A sequencing impossibility (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-57-manual-hold-sentinel.md:32— "a spec is held by adding a native spec dependency on the sentinel (depends_on: [<sentinel>]); the run seam's selector already skips specs with a non-done dependency" - End B:
.abcd/development/intents/shipped/itd-80-intent-lifecycle-automation.md:41— "the store here is the minimal floor: link, status-by-directory, reconcile."
itd-57's whole mechanism is a depends_on edge on a sentinel spec, lifted with a native spec rm-dep. It relies on a run-seam selector that it says already skips specs with an unfinished dependency. itd-80, which delivered the native spec store, puts the dependency graph between specs out of scope. It describes the store as a minimal floor: link, status-by-directory, reconcile. As written, that store has none of the three things itd-57 builds on: the dependency edge, the rm-dep verb and the skipping selector.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1228.
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-2610262044454212 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262044454212-itd-57-holds-a-spec-back-through-a.md
open on GitHub ↗ · commit history ↗
References2
mentions5
- 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.
- iss-2610262039144591itd-57 unblocks a spec with a native `spec rm-dep`, but the spec verb registers only its bare board and `spec close`
- iss-2610262044240923The manual-hold draft relies on the selector skipping specs with a non-done dependency, but the shipped pick selects planned intents by their blocked_by edges