Backups

Tool: tools/ops/backup.sh (ships in the bundle). Runbook 16.

tools/ops/backup.sh backup <prefix>     # e.g. identia / legaldesign
tools/ops/backup.sh list
( cd data/backups/<id> && sha256sum -c SHA256SUMS.txt )
tools/ops/backup.sh verify data/backups/<id>    # throwaway, does not touch live
# DESTRUCTIVE:
tools/ops/backup.sh restore data/backups/<id> --yes

Volume prefix is read from the compose label on society-pg. Override: VOL_PREFIX=….

What it covers

Piece	How
DB society and LLM Router	pg_dump → db/*.sql
Volumes pg-data / vectordb-data / object-store-data	tar.gz
agent harness runtime + specs (data/, infra/data/, societies/)	tar.gz
Integrity	SHA256SUMS.txt + MANIFEST.txt

Template SOUL.md is already in git. The backup covers runtime state, not config-as-code.

verify brings up throwaway relational database :5499, vector index :6399, object store :9499, counts hosts/profiles/artifacts, collections, SOUL.md, buckets. Use it before trusting a backup and always before a client restore.

On client installations and reference client: daily cron 04:17 + verify, retain 7 days, on the box's local disk. Off-box copy: none. Relying on “there is always a rollback” without a green verify is a belief, not a capability.

data/backups/ is git-ignored. Do not commit it.

Restore overwrites DB, volumes and runtime. Recreating the relational database container does not lose data (pg-data persists); a logical restore does replace it.