memory-archive-superseded

# Memory Archive Superseded ## Purpose / When to Activate Activate when a DEC has been **formally superseded** by another DEC and you want to migrate its row out of the active index eager-load surface, while preserving full traceability and path stability. **Discovery-only.** This skill must NEVER be invoked by daemon delivery. Per base.rules.md, Delivery may only write memory via `decision-extraction` after QA PASS. Archive operations are a strategic memory governance act and belong to Discovery (or Bootstrap during initialization). **When NOT to activate:** - DEC is still active or candidate (no formal supersession) - DEC is `deferred` or `cancelled` (different lifecycle, different archive pattern) - The supersedeur DEC is not yet `active` (premature archival risk) - Pattern, ARCH, or strategy file supersession (V2 — out of scope this skill) ## Preconditions (must hold before execution) 1. Supersedee DEC has frontmatter `status: superseded` and `superseded_by: DEC-X` (or `[DEC-X, ...]`) 2. Supersedeur DEC file exists at `decisions/DEC-X.md` 3. Supersedeur frontmatter declares `supersedes: [DEC-Y, ...]` mentioning the supersedee 4. The supersedee is currently in active `index.md` (Active Files table and/or Decision Registry) 5. No active or in-progress backlog story is amending the supersedee DEC If any precondition fails: STOP and escalate. Do not partial-apply. --- ## Process ### Step 1 — Verify preconditions Read the supersedee DEC frontmatter. Read the superse...