phase membership and lifecycle directories disagree: planned intents (itd-20, itd-24, itd-29, itd-46) appear in no phase Scope, while draft itd-43 is scoped into Phase 0/1 yet listed later-phase. ADR-bound.

Frontmatter

.abcd/work/issues/resolved/iss-3-phase-membership-vs-lifecycle.md
open on GitHub ↗ · commit history ↗

Referenced by2

• iss-704-scope.md hand-maintains intent counts (thirteen phased intents) that the phase docs and planned corpus have outgrown.blocks
• iss-803-out-of-scope.md omits current drafts itd-74 and itd-75 while including scoped itd-43; regenerate from the actual draft corpus.blocks

mentions11

• adr-34Intent lifecycle and phase scheduling are orthogonal axes
• dcn-26082400000000022026-08-24 — Bug-hunt round 5 (bughunt-a): baseline green; five parallel
• iss-2608240806090544planned/README.md categorically claims every intent carries a spec_id: spc-N link, but 20 of 43 planned intents have spec_id: null — a legal lint-enforced state (intent_lifecycle) per the surface contract, parent intents/README, and adr-34; the subheading silently reintroduces the over-narrow framing adr-34 already corrected in the parent README (resolved iss-3).
• itd-4Nothing You Notice Gets Lost
• itd-20`/abcd` Tells You Where You Are
• itd-24Completed Releases Get A Retrospective
• itd-29Domain Experts Run A Spec Autonomously And Recover From Anything Without Touching Git
• itd-43abcd Speaks One Word for a Specced Block of Work, and That Word Is "Spec"
• itd-46`/abcd:intent "<text>"` And `/abcd:capture "<text>"` Become Symmetric Create Paths
• itd-114Two Agents Can Mint At The Same Instant And Never Collide
• itd-2609091034175565Before an agent starts on an item, it reserves it on the shared remote, and everyone who works on the project sees the reservation