rollback

To revert system state to a known checkpoint, you command a rollback that restores the system to a previously captured checkpoint. This action enforces checkpoint usage and verifies the post-rollback state matches the checkpoint.

The best way to safely undo file mutations when verification fails is checkpoint-based restoration. It reverts changes to a validated state with provenance, ensuring scoped recovery for only the intended files.

A rollback maintains an audit trail by documenting evidence of what was changed and why. This ensures auditability by maintaining an evidence trail of the restoration process following the CAVR pattern.

Yes, you can restore only the intended files or state when required. The rollback mechanism supports scoped recovery, allowing targeted restoration to a validated checkpoint without affecting unaffected areas.

You should trigger a system rollback during verification failures, errors, or explicit undo requests. It provides a safe, auditable way to reduce risk by restoring the system to a known checkpoint rather than attempting manual fixes.

Yes, rollback verifies the post-rollback state matches the checkpoint. It enforces checkpoint usage and explicitly validates the restored state to ensure the mutation was completely and safely undone with documented evidence.