pinax-proof-maintenance-operator

Pinax maintenance workflows can be safely executed on a local vault using proof loops, snapshots, and approval gates to ensure all changes are validated and reversible. The workflow guides you through diagnosis, planning, and application with explicit safety checks.

A proof loop is a maintenance execution pattern that safely runs Pinax diagnostics, plans changes, and applies repairs iteratively. It protects your vault by requiring validation and approval gates before modifying notes, ensuring unsafe changes are caught before application.

Yes, you can restore your local vault to a previous version after running metadata repair because the workflow creates version snapshots before applying changes. These snapshots capture the vault state, allowing you to revert if the repair or organize operation causes issues.

Approval gates are integrated into the maintenance workflow to ensure safety for high-risk tasks like metadata repair, organize, and record maintenance. They require explicit validation before changes are applied, preventing unintended modifications to your local vault.

The best way to diagnose vault issues before applying changes is running the doctor and stats commands within the proof loop workflow, which provide explicit diagnostics for planning safe repairs. This diagnostic phase ensures you understand the vault state before proceeding.

You should avoid automated maintenance workflows when your local vault contains unsaved states or lacks recent version snapshots, as the workflow relies on existing snapshots for reversibility. Ensure a valid snapshot exists before attempting metadata repair or organize operations.