Back up and restore

Outcome

A named recovery point restores semantic state and verifies every referenced immutable artifact before work resumes.

Prerequisites

Define the recovery-point and recovery-time targets, database backup/PITR policy, independent logical export, object replication policy, encryption keys, and a clean restore environment.

Steps

1. Stop new commands and schedules while preserving read access where safe.
2. Restore PostgreSQL to an isolated environment from the selected recovery point.
3. Restore or mount the immutable artifact namespace and run the database/object consistency scan.
4. Validate migrations, tenant constraints, event order, and sampled evidence digests.
5. Reconcile Temporal open work and external provider state against PostgreSQL intent.
6. Resume a synthetic run before reopening real work.

Local Slice 0 proves process restart, not a production backup restore. Managed database and object restore evidence activates with the release infrastructure.

Verify

An exported project opens from the restored environment, sampled evidence bytes match their manifests, and no workflow result mutates a stale generation.

Recover

If reconciliation finds missing bytes or ambiguous external operations, keep affected evidence unavailable and work paused. Restore from another replica or re-create only from a proven source; never invent a successful manifest.

Next task

Define retention and deletion.