coulomb-social/docs/release/provider-kit-recovery-post-date-2026-10-31.md
tegwick b001cdd07f
Some checks failed
Use-case regression gate / usecase-regressions (push) Failing after 7m13s
Protect corrected-date recovery kit and refresh generation review
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a18e2d-f513-7742-b8e7-12af0b744ff3
2026-10-31 08:43:20 +01:00

4 KiB

Protected recovery of the corrected-date point

The 2026-10-31T07:13:52Z paired point is now protected outside rolling expiry, together with the captured application image, PostgreSQL image, SDK and recovery tools. The immutable kit is 276,019,200 bytes, SHA-256 4166eb8ba97f7bd79e912c2efaee2622fcd472b05ed80070ccf7e6728fec5bd6, version 1793432303941465. The prior October29/30 kits remain retained.

The independent reader retrieved the complete kit. Before loading images or running included tools, every one of its 2,098 members matched the manifest size/hash. The decryption identity came from the separate protected provider escrow. No original node, local plaintext backup, personal Console session or registry pull was used. The already installed bootstrap API client, Python/age and Docker daemon remain prerequisites; this is not a fresh-machine or operator-account recovery test.

Provider retrieval, validation, image load, decryption, isolated database/content restore and application checks took 46.692 seconds. All 13 tables/114 rows/sequences and 86 files match. The captured package renders all 40 owner pages, denies all 40 ungranted requests, and passes synthetic viewer-read/mutation-denial checks. Fixtures roll back and source file hashes stay unchanged. There are no published container ports and no production restore. This is not a real-browser identity journey or acceptance of productive user flows.

The successful recovery proof is separately protected at version1793432409572654, SHA-256 b93e3003627581eb510086ba207bf283085d88cb9b3dfd0e74ffa8ebf02c39f0, with independent exact-byte readback. The newly created temporary drill identity file was removed after success; permanent custody and historical copies are untouched. The application data in the kit is encrypted; API pairs and private identities are excluded from it. Existing bucket versioning and absent lifecycle rules were checked.

The kit deliberately contains captured image51281946 (revision18), not later live image522bcd7f. Both images already passed the same corrected-data view checks, and the live package exported that point successfully in the release-return evidence. Recovery of this kit does not itself authorize a production restore or upgrade.

The platform owner's public custody contract had still pointed to October29. Its protected_recovered_point now identifies this newer independently proven point and its kit/proof references; credential material coordinates and grants are unchanged. The immutable kit includes the historical bootstrap-contract snapshot for escrow retrieval. Its explicit primary receipt and manifest bind the recovery point; that embedded historical pointer is not a live latest-kit index.

Generation review

The refreshed scoped provider observation covers five logical points, five primary versions, ten mirror versions and eight protected-kit/proof/fixture versions. Fifteen exact-version HEADs match, and all three retained worker public receipts pass independent byte comparisons. No delete marker is present. Primary global 30-day expiry remains as observed; mirror and kit buckets have no lifecycle rules.

The existing 14-daily/four-weekly selector keeps three points (October29, October30 and October31 at07:13), including the newest successfully recovered point. The October31 00:27 and02:07 mirror points are expiration candidates only; both remain retained. Three days of observed history do not prove 14 days/four weeks of available backups. Unknown objects, fixtures and all protected kits are preserved. The old6af0564e expiry proposal predates this inventory and protection binding; refresh/rebase it before any eventual attended expiry, after the existing caller admission and boundary proofs. No deletion, IAM/bucket-policy update or timer activation occurred.

Evidence: companion provider-kit JSON/source manifest and generation-retention-post-date-2026-10-31.{json,sources.txt}. Private observation, inventory and complete selector output are under ~/.config/railiance-platform/coulomb-social-recovery/retention-post-date-20261031/.