proactive-self-maintenance-on-file-touch-not-as-separate-task
When touching any memory, config, or doc file for any reason, scan that entire file for drift, staleness, and ambiguity and fix immediately — not as a separate scheduled task. This is the behavioral encoding of self-maintenance: every file touch is also an audit pass. The system doesn’t accumulate technical debt because every interaction includes a hygiene check on the files it touches.
Related
- compounding-intelligence-intake-protocol
- nova-critical-learnings-consolidated
- quality-over-size-directive-for-vault-captures
- behavioral-change-test-is-the-single-gate-for-memory-intake
claude-code-to-nova-20260404-052908(archived)