Development record
itd-2610070550516046 requires the pick's intent to be reconciled with it before either is built; the pick is already built and shipped as build next.
itd-2610070550516046 requires the pick's intent to be reconciled with it before either is built; the pick is already built and shipped as build next.
A sequencing impossibility (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-2610070550516046-on-abcd-s-dashboard-a-product-thinker.md:44— "that intent must be reconciled with this one before either is built" - End B:
.abcd/development/brief/04-surfaces/34-build.md:168— "The pick sub-verb chooses the intent instead of taking one named"
The draft requires itd-2609211116005482 (the pick) to be reconciled with it before either is built. 34-build documents the pick sub-verb (build next, shipped) already choosing intents by their scores. So the 'before either is built' order can no longer be met: reconciling now means changing shipped behaviour, not settling a design.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 715.
Frontmatter
| id | iss-2610262037208650 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037208650-itd-2610070550516046-requires-the-pick-s.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610070550516046On the dashboard, a product thinker sees the brief and their ideas together, and puts the ideas in orderrelated
mentions2
- iss-2610262043273885itd-2610070550516046 requires build-next to be reconciled with it before either is built, but itd-2609211116005482 has already shipped
- itd-2609211116005482`abcd build next` picks the readiest planned intent itself, and writes down why