📖About & Usage

About

DB Lock Watch is a small watchdog droid owned by Hermione. Every 15 minutes it checks whether the SQLite databases behind the plan generator and Carol Initiatives have a write lock held abnormally long — the usual signature of a leaked transaction that never committed or rolled back. When it finds one, it names the longest-lived lock holder and files a deduplicated incident so the leak gets repaired before it quietly stalls the database.

Its routine is deliberately gentle: it is read-only over real data and only takes-and-rolls-back a write lock to measure contention. One open incident is kept per database, so repeated breaches update the same report instead of spamming. It runs on the schedule registry (see Scheduled Processes) and feeds the wider Process Monitoring and Carol Infra Monitor observability picture.

Its exact name is unique, and its family is recorded as "(none)" — so in practice it is a one-off — though 222 droids share that same unnamed family slot across many owner agents, meaning the watchdog pattern itself is common. The engine is pure software: it makes no Claude calls, so there is no model involved.

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.