Self-maintaining workspace: severity-based dual-gate hygiene

Decision

Implemented 8-check startup scan + 7-action session-close cleanup extending existing hookify rule and session-close skill. CRITICAL findings (secrets, broken symlink) block immediately. WARN findings (bloat, staleness, drift, redundancy, ambiguity) queue for session-close.

Rationale

31-Mar-2026 audit found 15 issues (API keys, split-brain memory, 71 bloat entries, count drift, dead files). All were preventable with automated checks at session boundaries. Chose session-boundary enforcement over real-time hooks to minimize overhead and leverage existing infrastructure.

Alternatives Rejected

• Option A (hooks only): catches at creation but can’t detect passive decay\n- Option B (session boundaries): chosen — extends existing infrastructure, catches both active and passive issues\n- Option C (cron-based): requires new infrastructure, runs even when no sessions active

Outcome

Pending

Related

• clawteam-openclaw-multi-agent-swarm-evaluation
• workspace-memory-split-brain
• enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
• claude-code-to-nova-enterprise-backup-v3-2026-03-25 (archived)
• claude-code-to-nova-20260327-090715 (archived)