Deep VPS audit 2026-05-03 shipped 5 architectural fixes: (1) self-maintenance-discipline.md NEW topi
What
Deep VPS audit 2026-05-03 shipped 5 architectural fixes: (1) self-maintenance-discipline.md NEW topic file (Tier 1 Directive #7 detail extracted from MEMORY.md); (2) vault-pruning-policy.md NEW topic file (tier-aware retention codified, banning bulk-archive-on-consultation-recency); (3) drift-check cron re-enabled (nightly 17:00 UTC); (4) mem_limit pattern applied to 16 containers (defense-in-depth, Law 11); (5) backup-log-permission silent-failure pattern caught + fixed across 6 logs. Plus 6 evolution-backlog items added.
Why
Routing knowledge needs updating: (a) drift-check cron now active again after 14d hiatus — its findings will surface to vault errors; (b) vault-pruning-policy changes how unconsulted notes should be interpreted (institutional ALWAYS-RETAIN, not bulk-archive); (c) self-maintenance-discipline canonical pattern now lives at separate topic file, not inline in MEMORY.md; (d) build-autoloader-registry.py recreate is in backlog — orchestrators should know the registry is a manual-edit point until rebuilt.
Action Required
Review new topic files. Update orchestrator routing decisions if applicable: (i) on next vault unconsulted alert, apply tier-aware policy not bulk-archive; (ii) on next infrastructure capability addition, follow self-maintenance-discipline canonical cron pattern (steps 1-8); (iii) defer Phase 1.5 capability sync for blue MCP until next dedicated session.