Development record
universal patterns says issue-ledger entries cannot change after creation; launch has the deferral verb write a waiver into an open record
universal patterns says issue-ledger entries cannot change after creation; launch has the deferral verb write a waiver into an open record
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/05-internals/04-universal-patterns.md:195— "capture issue-ledger entries (immutable post-create)" - End B:
.abcd/development/brief/04-surfaces/04-launch.md:598— "deferral_reason, both schema-accepted keys, written by the ledger's deferral verb"
The artefact-lifecycle table puts issue-ledger entries in the append-only class: never modified after creation. Launch's findings gate depends on records being changed after capture: the ledger's deferral verb writes the deferred_after and deferral_reason pair into the record's frontmatter, and a record may be re-graded. A ledger whose entries never change could not hold either.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 305.
Frontmatter
| id | iss-2610262032428223 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262032428223-universal-patterns-says-issue-ledger.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610262036573008The lifecycle taxonomy calls issue-ledger entries immutable after creation, while the drain's user-visible route writes `related_intents` into the issue
- iss-261026203949497904-universal-patterns classes issue-ledger entries as immutable once created; itd-4's `capture resolve` moves an entry and adds a resolution note.