itd-34 maps a standalone intent one-to-one to a flow-next spec; the surfaces register says an intent owns one or more specs in the native spec store.

itd-34 maps a standalone intent one-to-one to a flow-next spec; the surfaces register says an intent owns one or more specs in the native spec store.

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/04-surfaces/README.md:275 — "an intent owns one or more specs"
• End B: .abcd/development/intents/shipped/itd-34-three-intent-kinds.md:21 — "A standalone intent maps 1:1 to a flow-next spec"

itd-34's press release and lifecycle paths say a standalone intent maps 1:1 to a flow-next spec, planned through /flow-next:plan. The README's spec row describes the native spec store, where spec close ships an intent only when no open spec still names it, because an intent owns one or more specs. The two documents disagree on which store holds specs and on how many specs one intent can have.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 886.

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. itd-34's one-to-one mapping and flow-next plan path are the earlier model; the accepted ADR and its dcn record say which holds.