📖About
Public write-up withheld. The input contains operational source material but does not include the publication contract or verified approval for its public projection.
📖Usage
Proceed only after the owning app’s declared public fields are retrieved and validated through shared.carolopedia_publication, with a valid provenance receipt written atomically with the page.
📖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.