This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-67 picks the release bump tier from phase-completion detection; the intent chapter derives the version from each intent's impact judgement

issuewontfixminoriss-2610262035142666

itd-67 picks the release bump tier from phase-completion detection; the intent chapter derives the version from each intent's impact judgement

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

  • End A: .abcd/development/intents/shipped/itd-67-installable-versioned-plugin.md:47 — "/abcd:launch ship auto-selects the bump tier (patch/minor/major) via the brief §4 phase-completion detection"
  • End B: .abcd/development/brief/04-surfaces/05-intent.md:393 — "the compatibility judgement the derived version is computed from"

itd-67 has /abcd:launch ship choose patch, minor or major through the brief's phase-completion detection. The intent chapter says the intent's impact field is the compatibility judgement the derived version is computed from, and elsewhere says phases are retired. Two incompatible inputs are named for the same bump decision.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. Same superseded heuristic as the other itd-67 phase-detection records; the version is computed from the records' impact.

Frontmatter

idiss-2610262035142666
typeissue
lifecyclewontfix
severityminor

References1

mentions1