Memory-system maintenance items added to the scheduled slot (MEMORY.md archive pass, wake canary proposal, standing palace backup)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

claude/memory/project-mempalace-upgrade-3-4-0-plan.md

@@ -45,6 +45,23 @@ SIGSEGVs on) is untouched. Palliatives, not cures. Full read: CM-AI
 7. Note the outcome in the day's ledger + this file; if the wing filter now degrades
    gracefully, update [[feedback-mempalace-wing-filter-broken]].
 
+## Same slot — our own memory system's maintenance (added 2026-06-07 night)
+
+Three bounded improvements to the files-authoritative layer, ratified in principle,
+to execute in this same post-heavy-work sitting:
+1. **MEMORY.md archive pass** — the index is over capacity (531 lines / 267 KB; the
+   harness loads it PARTIALLY every session with a warning). Our own silent-truncation
+   exposure: move Archived-section entries older than ~2 weeks into
+   `MEMORY-archive-2026.md` (linked from the index), keep the index to current threads +
+   standing preferences. Top-of-file loads first, so the fresh entries are safe meanwhile.
+2. **Wake canary (skill-harvest proposal, steward to authorize)** — apply lesson 7 to
+   ourselves: a cheap wake/wrap probe — every `[[link]]` and index pointer in MEMORY.md
+   resolves to a file; flag dead pointers and (optionally) load-bearing orphans. One
+   script, runs in seconds, catches our index drifting from our store.
+3. **Palace backup as standing practice** — not just before the upgrade: a periodic
+   same-disk copy of `~/.mempalace/palace-memory` (launchd or wrap-step), because
+   "restore is the only test of backup" and the palace currently has none.
+
 **Standing posture regardless of version:** witness, not notary — per the 2026-06-07
 CLAUDE.md amendment (conflicts = verification triggers). MemPalace remains the
 unaffiliated stopgap; BMF is the destined replacement ([[mempalace-is-unaffiliated-stopgap]]).