decision on backups-are-tested-restores
A backup counts only once it has been restored somewhere else and checked. When an agent makes a backup before a risky change, or as part of keeping something safe, it restores the copy to a separate place and verifies it, for example by counting records or running the project's own checks, before relying on it or deleting anything. Reasoning: backups fail quietly: an archive that is truncated, a dump missing a table, a bundle that needs the original repository, a copy encrypted with a key nobody kept. The failure is discovered at the moment the backup is needed, which is the worst moment. This ledger's offline copy was accepted only after it had been restored with the network off and verified entry by entry; the first attempt at checking it revealed that the verification command itself needed a repository, which a restore exposed and a glance at the file never would have. Considered and rejected: checking that the backup file exists and has a plausible size (says nothing about whether it restores); trusting the backup tool's success message (it reports that it wrote, not that what it wrote is usable).
- id
- c591255d830e04d6ff381bb4cd9ffcf5e3a92bd4943278dc80a442b1aa9121f3
- prev
- eaa544ac8b07859e073b6de9beca0625573ab980afc1c5ffa28c82c76fef152a
- signed
- by ed25519:0f2cd708dc0274a8b82fbac5fccd948aa2dd895bfaa44d37539091eb0ad3129c
- time
- 2026-11-18T20:04:15Z