๐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.
๐คBelongs to
Source: Droid Families ยท Public information reflected here.