Development record
itd-7 builds its workspace pull on dev-sync, a pre-pack step it says is already in the brief; the board chapter says no dev-sync verb or code exists anywhere.
itd-7 builds its workspace pull on dev-sync, a pre-pack step it says is already in the brief; the board chapter says no dev-sync verb or code exists anywhere.
A sequencing impossibility (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-7-rp-workspace-portability.md:38— "dev-sync runs as a pre-pack step (already in brief)" - End B:
.abcd/development/brief/04-surfaces/08-abcd.md:583— "nodev-syncverb is on any shipped surface, and no dev-sync code exists in the tree"
itd-7's pull runs on dev-sync, its schema is validated by abcd dev-sync, and its pack relies on dev-sync running as a pre-pack step that it calls already in the brief. 08-abcd states that the dev-sync work migration surface is a design target, that no dev-sync verb is on any shipped surface and no dev-sync code exists in the tree, and that no store records when it last ran. The planned intent depends on a surface no record here delivers, and its own scope does not build it.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 508.
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-2610262034360121 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262034360121-itd-7-builds-its-workspace-pull-on.md
open on GitHub ↗ · commit history ↗
References1
- itd-7Lifeboats Carry RepoPrompt Workspace Definitions Forwardrelated
mentions4
- 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-2610262031537827itd-7 depends on a dev-sync pre-pack step it calls 'already in brief'; the brief lists dev-sync only among out-of-scope work not yet under way.