This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-80 moves an intent to shipped when its linked spec closes; invariant 17 says a close never ships an intent that another open spec still names

issuewontfixminoriss-2610262032168367

itd-80 moves an intent to shipped when its linked spec closes; invariant 17 says a close never ships an intent that another open spec still names

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

  • End A: .abcd/development/intents/shipped/itd-80-intent-lifecycle-automation.md:34 — "on spec close, detect the linked intent via the immutable link, move it planned → shipped with an atomic same-filesystem rename"
  • End B: .abcd/development/brief/02-constraints/03-invariants.md:171 — "closing a spec never ships an intent that still has an open spec, the intent moves planned/ → shipped/ on the close after which no open spec names it"

itd-80's reconcile finds the linked intent through the immutable link when a spec closes, and moves it planned → shipped. Invariant 17 makes the intent↔spec relation 1:n: closing a spec never ships an intent that still has an open spec, and the move happens only on the close after which no open spec names it. The two reconcile rules disagree about which close ships the intent.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. closeShips in the CLI moves only members no other open spec names; itd-80 describes the original one-spec reconcile.

Frontmatter

idiss-2610262032168367
typeissue
lifecyclewontfix
severityminor

References1

mentions1