Backup rulings: 2026-08-14
Owner Q&A, 2026-08-14. Closes the open halves of
docs/proposals/2026-08-07-backup-schedules.md (§3/§4/§6),
docs/proposals/backup-manifest-in-repo.md (acceptance proof), and the
archive register §40.8 item 1.
| # | ruling | consequence |
|---|---|---|
| B1 | The armed nightly schedule set is RATIFIED and gets CODIFIED: build the shc_backup_schedule terraform resource and land backup.tf (schedules + the 7/4/12/5 retention pin) in both ops repos. | The schedules proposal’s §3/§4/§6 close; an estate rebuild reproduces the posture. |
| B2 | The traefik row goes WEEKLY (from nightly). | One ingress blip a week; at most a week of ACME renewals lost, re-issuable. |
| B3 | Standing proof-of-content: weekly budget-capped verify --deep cron of the newest good archive per deployment, plus a restore rehearsal each disposable-estate campaign. | Content rot and restore-path rot both get standing coverage. |
| B4 | Quiesce hold stays 300 s global with per-stack overrides for known long captures (openobserve first). | Matches the 2026-08-02 stopped-beats-untrusted ruling. |
| B5 | Offsite: ONE S3 provider, Hetzner, and that is final. Owner verbatim: “we have 1 s3 provider which is from hetzner and that’s how i want it. all backups go to it. i’ll do my own truenas or whatever setup myself later to keep the s3 backed up.” | No second-repo product feature, no WebDAV deposit consumer for backups. Downstream replication is the owner’s own infrastructure, outside the product. |
| B6 | One S3 per estate; owner verbatim: “dude 1 s3 per estate.” Measured reality (2026-08-10) violates this: one project-wide key, byte-identical on both estates, able to delete every archive of both. | Owed: separate Hetzner object-storage credentials (and buckets/projects as needed) per estate, keys swapped via vault. Hetzner’s Cloud API has no object-storage surface, so the credential mint is console work, owner-gated; the vault swap + verification can be prepared. |
| B7 | One combined disposable-estate proof campaign is AUTHORIZED: cross-cluster recover (manifest-in-repo acceptance), the quiesce stop-escalation live proof, and a full restore rehearsal including the GitLab clone-out, in a single spend. | Closes §40.8 items 3/4, marks backup-manifest-in-repo landed, promotes HANDOFF §6.2 to restore-proven. |
| B8 | The native .bak envelope plan is RETIRED permanently. The restic seal is the product’s only encryption-at-rest story; no-repo estates keep loud local plaintext by design. | §40.8 item 1 closes. One format to verify, rotate, migrate, forever. |
| B9 | Cadence stays scope-based; no per-app data-class axis for now. (default carried from the lane’s recommendation; revisit only if per-stack rows proliferate) |
shc@docs:~$