📖About & Usage

About

The Registry Journal Custodian is a scheduled watcher droid owned by Hagrid. Every fifteen minutes it checkpoints the registry's write-ahead file into the main database, folding committed changes into durable storage while the system keeps running with no downtime. It exists because journal repair is best handled as a scheduled maintenance action with one accountable owner — if every process tried to fix it on its own read path, it would never succeed.

On each run it drains the write-ahead file, attempts the journal restore (reporting any refusal rather than hiding it), and keeps exactly one standing alarm raised while the estate is too busy for the restore to complete. It also watches for side-file copies that still hold data: a non-empty side-file contains committed changes, so it never deletes one — moving one aside is the action that would actually lose registry data. The restore only succeeds when no other connection is attached, so it needs a managed apps-stopped window arranged through Radagast. Its schedule is tracked in Scheduled Processes.

It is one of 15 droids in the watcher family (see Droid Families) — a standard, reusable family that several other agents also run — though the name "Registry Journal Custodian" itself is unique. Its execution engine isn't recorded yet, so it's not currently known whether this droid is pure software or calls Claude.

👤Owner

📚Recent initiatives

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

No initiatives recorded for this droid yet.