Development record
itd-34 links a bundle member to its shared spec through epic_id and an epic.intent list; the intent surface page links it through spec_id and the spec's intents list.
itd-34 links a bundle member to its shared spec through epic_id and an epic.intent list; the intent surface page links it through spec_id and the spec's intents list.
A naming conflict (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-34-three-intent-kinds.md:52— "each intent'sepic_id: spc-Nandbundle: <bundle-id>" - End B:
.abcd/development/brief/04-surfaces/05-intent.md:235— "links each spec_id to the shared spec"
itd-34 says each bundle member carries an epic_id naming the shared spec, beside bundle, and that the spec lists its members as epic.intent. 05-intent.md says the bundle command links each member's spec_id to the shared spec and mints the spec with an intents: list beside intent:. Two names for the one intent-to-spec link: a member written to itd-34's shape carries a key the lifecycle rules and the readers described on the surface page do not read.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 529.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262045336833. Same A wording (epic_id on bundle members) and same root cause; the bundle code writes spec_id (internal/core/intent/bundle.go).
Frontmatter
| id | iss-2610262034528274 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262034528274-itd-34-links-a-bundle-member-to-its.md
open on GitHub ↗ · commit history ↗
References1
- itd-34Intents Promote In Three Flavours — Standalone, Bundle-Member, Disciplinerelated
mentions2
- 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.
- iss-2610262045336833itd-34 has bundle members share an epic_id field; itd-43 says the intent field is spec_id and epic is gone