04-universal-patterns classes issue-ledger entries as immutable once created; itd-4's `capture resolve` moves an entry and adds a resolution note.

04-universal-patterns classes issue-ledger entries as immutable once created; itd-4's capture resolve moves an entry and adds a resolution note.

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/intents/shipped/itd-4-issue-capture.md:36 — "move to resolved/ with optional resolution note"

The lifecycle taxonomy puts capture issue-ledger entries in the append-only class: never modified after creation, old entries kept verbatim. itd-4 defines capture resolve as moving the record to resolved/ with an optional resolution note, and gives every record an updated field. An entry that changes folder and gains text after creation is not immutable. The same table also lists the ledger as compounding-curated.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262032428223. Same End A; resolve moves the record and adds a note, as itd-4 and the code do.