docs: consolidate repository guides and preserve audit history

2026-09-11 14:22:41 +02:00
parent 115441a409
commit 682a3028bb
404 changed files with 3402 additions and 2621 deletions
@@ -0,0 +1,13 @@
+# Operational backups
+
+A complete recovery set includes the database, uploaded/CV data, exports where needed, Data Protection keys, and account-deletion tombstones. SQLite has an application backup path; MariaDB/MySQL must use the external server backup path. Retention and remote encrypted-copy settings are configured through `BACKUP_*` variables.
+
+The operator must periodically prove backup freshness, manifest completeness, restore correctness, key availability, and post-restore deletion semantics. A backup that exists but cannot restore the application data and keys is not a verified backup.
+
+The seeded MariaDB backup → restore → application-start rehearsal and the later read-only production
+checkpoint are historical evidence, not proof of a current production restore. They remain recoverable
+in the [pre-cleanup backup verification record](../_archive/pre-docs-cleanup-2026-09-11/docs/operations/production-backup-verification.md).
+
+The pre-cleanup operator handoff recorded production Data Protection key rotation as complete on
+2026-08-02. Current key custody, recovery-set inclusion, and post-restore decryption still require
+verification.