itd-73 derives a major bump from any breaking intent; 04-launch says no set of records derives 1.0.0 from a 0.y.z base

itd-73 derives a major bump from any breaking intent; 04-launch says no set of records derives 1.0.0 from a 0.y.z base

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

• End A: .abcd/development/intents/shipped/itd-73-derived-versioning.md:30 — "take the highest-severity impact, and compute the next SemVer — any breaking → major, else any additive → minor, else patch"
• End B: .abcd/development/brief/04-surfaces/04-launch.md:534 — "No set of records derives 1.0.0 from a 0.y.z base."

itd-73 states its derivation rule with no condition: any breaking impact is a major bump. 04-launch's bump-tier table maps breaking to a minor bump before 1.0.0 and says no set of records derives 1.0.0 from a 0.y.z base. At a 0.y.z version, a breaking intent gives 1.0.0 under itd-73 and a minor bump under 04-launch, so the two rules cannot both hold.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The unconditional rule is the stable-version case; the later pre-1.0 row (breaking bumps the minor, no input derives 1.0.0) is documented in the ADR amendment and the code.