{"wiki":{"id":2993,"slug":"hg-regjournal-01","entity_type":"droid","entity_id":"hg-regjournal-01","title":"Registry Journal Custodian","prose_md":"## About\n\nThe Registry Journal Custodian is a scheduled watcher droid owned by [[agt_015]]. 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.\n\nOn 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 [[agt_029]]. Its schedule is tracked in [[scheduled-processes]].\n\nIt 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.","namesake_json":"{\"engine\": \"unknown\", \"model\": null, \"claude_purpose\": null, \"family\": \"watcher\", \"family_size\": 15, \"is_unique\": false}","profile_pic_path":"","source_hash":"4071b03d8457325412b998dc731e7ed0f52b34d84ce7dc2a2c970ae2e0bad330","status":"active","last_generated_at":"2026-08-05 03:28:14","created_at":"2026-08-05 03:27:54","updated_at":"2026-08-05 03:28:14"},"facts":{"id":"hg-regjournal-01","name":"Registry Journal Custodian","machine_name":"HG_REGJOURNAL_01","owner":"agt_015","function":"Drains the registry write-ahead file into the main database every run (works live, no downtime), attempts the restore to rollback journalling, and raises exactly ONE standing alarm while the estate is too busy for it. Also watches for side-file copies that still hold data — moving one aside is the action that actually loses committed registry changes.","process_type":"scheduled","schedule":"*/15 * * * *","process_name":"","avatar_color":"#94a3b8","created_for":"CAROL-INI-3548","purpose":"Owns the registry's journal durability, so the repair is a scheduled maintenance action with one accountable owner instead of a write attempted from every process's read path, where it could never succeed.","duties":"1. Checkpoint the write-ahead file each run so committed changes are folded into the main database. 2. Attempt the journal restore; report refusal, never swallow it. 3. Keep exactly one alarm standing while the condition persists, and close it when it clears. 4. Alarm critically if a side-file copy holding data is found outside the database.","constraints":"The restore succeeds only when no other connection is attached, i.e. under a managed apps-stopped window arranged through Radagast. On a live estate the drain still runs and keeps the exposure near zero. Never deletes a side-file: a non-empty one holds committed data.","status":"running","gender":"","archetype":"watcher","building_block":"backup_on_machine","service_override":null,"enabled":1,"task_key":"backup.registry_custody","model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}