feat(ai): add safe benchmark harness

2026-08-15 19:24:02 +02:00
parent 842e793f69
commit f7312f4ba6
14 changed files with 793 additions and 51 deletions
@@ -18,6 +18,19 @@
 The commands below are the ones to run against production. They are recorded so the owner can execute
 the same sequence with production values substituted.

+## 2026-08-15 read-only production checkpoint
+
+The earlier access statement above remains historically accurate for the 2026-07-19 rehearsal, but access is now available. A strictly read-only production inventory found:
+
+- 21 MariaDB `.sql.gz` dumps (about 5.2 MB combined), all passing `gzip -t`;
+- oldest observed dump: 2026-07-19 21:41 UTC; newest: 2026-08-02 17:32 UTC;
+- no JobTracker systemd timer or current-user cron entry;
+- 1.4 TiB free on the Docker/data filesystem and 36 GiB free on the 83%-used root filesystem;
+- database-only dump files in the backup directory: no owner-file volume, data-protection-key, protected tombstone, or configuration recovery bundle;
+- no restore, row/content read, count comparison, non-ASCII check, or production mutation.
+
+This upgrades production dump *presence and compressed-stream integrity* from unknown to observed, but it does not close the restore/RPO/completeness checklist. The newest observed dump was 13 days old at capture. See `docs/production/production-ai-hardware-assessment.md` and `docs/production/production-ai-rollout-and-rollback.md`.
+
 ## 1. Backup configuration

 Read from `deploy/deploy.sh` and `docker-compose.yml`: