This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-34 maps a standalone intent to a flow-next spec made by /flow-next:plan; itd-80 has intent plan mint a native spc-N record

issuewontfixminoriss-2610262045357230

itd-34 maps a standalone intent to a flow-next spec made by /flow-next:plan; itd-80 has intent plan mint a native spc-N record

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

  • End A: .abcd/development/intents/shipped/itd-34-three-intent-kinds.md:21 — "A standalone intent maps 1:1 to a flow-next spec"
  • End B: .abcd/development/intents/shipped/itd-80-intent-lifecycle-automation.md:31 — "A minimal native spec store (internal/core/spec): directory-as-truth spec records"

itd-34 says a standalone intent maps one to one to a flow-next spec and that its plan path calls /flow-next:plan and plan-review. itd-80 builds a native spec store in internal/core/spec, where abcd intent plan mints the spc-N record and the link itself. The two shipped records disagree on which store a spec lives in and which tool makes it.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. internal/core/spec is the spec store and PlanBundle mints a native shared spec; itd-34's own spec_id is a native spc id.

Frontmatter

idiss-2610262045357230
typeissue
lifecyclewontfix
severityminor

References2

mentions1