Notebook Entry 019
Maintenance Automation Pattern — When You Fix It Twice, Automate It
May 2, 2026
Why does the same manual fix keep recurring, and when do I automate it instead?
What happened
VAULT-INDEX.md was stale (stuck at Session 33) because the close protocol deliberately excludes VAULT-INDEX updates — they were displaced to "scheduled tasks" that don't exist yet. The manual fix took 2 minutes, but this is the second time it's happened.
Root cause
The close protocol was designed minimal (2 items) to succeed when energy is low. Maintenance tasks were displaced to automation that hasn't been built yet. The gap between "designed to be automated" and "actually automated" creates recurring manual fixes.
What changed
Manual fix applied. Heartbeat extension proposal captured for Phase 4 (F1). Pattern documented here.
The lesson
When you catch yourself doing the same manual fix twice, that's the signal to automate it. The gap between "displaced to automation" and "automation built" is where maintenance debt accumulates. Track these gaps explicitly — they're your automation backlog.
One implementation insight every other Tuesday.
What actually works when you ship AI in real organizations. Nothing you could get from a press release.