method-rules-maintenance-ruleslisted

# Post-LOCK maintenance rules (normative) The single source of truth for everything that happens to an idea AFTER its MVP scope is locked: drift, reconciliation, current-truth projections, cycles, and validation runs. Design converged via adversarial review (design record in the plugin repo's git history). Read together with the `method-rules-gate-contracts` skill, the `method-rules-artifact-schema` skill, and the `method-rules-state-schema` skill. ## 1. Mutation policies (replace any "living vs record" intuition) Every artifact has exactly one policy; semantic role never overrides it. | Policy | Meaning | Applies to | |---|---|---| | `append-only` | Rows/items are added, never edited, deleted, or reordered (byte-exact prefix — hooks enforce without whitespace trimming) | decision-log, evidence-ledger, drift-inbox, founder-charter (item level — see §7) | | `versioned-projection` | Current truth lives in the head version; a change = new file with `supersedes`; predecessor stays locked untouched | current-baseline, health-criteria | | `immutable-snapshot` | Frozen at its ceremony, never edited; changes happen only in a successor of the same kind or a new cycle | gate-locked artifacts, mvp-pack (frozen at LOCK — "build completion" is not a pipeline event), reconcile manifests + intake + claims registers, executed-kit snapshots, validation-run specs and reports | Post-LOCK disposition of surviving pipeline artifacts (complete matrix — nothing is unassigned): gate-locked arti