Development record
itd-2609231013154443 excludes intents with impact: internal; itd-73 defines impact as additive, breaking or fix only
itd-2609231013154443 excludes intents with impact: internal; itd-73 defines impact as additive, breaking or fix only
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-2609231013154443-every-release-arrives-with-its-own-press.md:106— "Intents withimpact: internal, and intents that left the record as Removed" - End B:
.abcd/development/intents/shipped/itd-73-derived-versioning.md:29— "additive(backward-compatible capability),breaking(incompatible surface or behaviour change), orfix(defect repair)"
itd-2609231013154443 leaves intents with impact: internal out of the release page. itd-73 defines the impact classification on every intent as exactly additive, breaking or fix, and derives the version from those three. A fourth value either exists and itd-73's derivation does not say what it does, or it does not exist and the exclusion names nothing.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1289.
Frontmatter
| id | iss-2610262045391451 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262045391451-itd-2609231013154443-excludes-intents.md
open on GitHub ↗ · commit history ↗
References2
- itd-73abcd Cuts the Version — You Never Type Onerelated
- itd-2609231013154443Every release arrives with a press release composed from what shippedrelated