# P26C2 R03 cleanup / recovery

This STEP changes no Machine Git source and no database schema.

Before semantic core acceptance, any failure is handled with idempotent cleanup:

- terminate the VM121 controlled live driver so its error cleanup removes synthetic DB/runtime state;
- disable any synthetic VM100 lifecycle peer and reconcile the agent to an empty desired set;
- delete the two temporary DDN `home-vm100` network namespaces/interfaces and root-only temp files;
- verify VM100 registry/runtime zero and VM121 business rows zero when possible.

A fresh encrypted PostgreSQL backup is created and restore-tested before live mutation. It is emergency recovery evidence, not an automatic rollback target.

Do not blindly restore the database after a late postcheck/report/publication failure. Once both external handshakes, both revoke effects, reissue rotation and final cleanup are accepted, later failures are continuation/publication failures and the live core must not be replayed destructively.