railiance-platform/docs/evidence/root-custody-history
codex a252447058
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Prove isolated custody recovery and prepare governed offsite finish
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a1029d-2c93-7500-a0e0-e3e089668b29
2026-10-03 20:47:48 +02:00
..
history
baseline.json
README.md

Non-authoritative publisher history recovery copy

This directory contains only the validated non-secret empty publication baseline and immutable history receipt. It is an independent recovery copy, not a read surface or a ceremony, and must never mint a grant. Runtime reads OpenBao only. Retain every newer publisher revision here; do not replace/remove old receipts.

The approved owner Forgejo repository backup contract covers source/history; this copy enters that established scope after commit/push. Exact remote Git retrieval/readback can prove this copy survives loss of the local publisher files. A fresh Nextcloud/Scaleway Forgejo archive containing this commit is a separate provider-generation proof and is not implied by push or Git readback. The attended finish helper instead directly encrypts retained publisher history and verifies upload/download/decryption using the current governed Nextcloud lane, reusing established owner storage and adding no new service or credential.

Controlled restoration copies baseline.json and history/ to the private operator state directory, preserves mode0600 and independently compares the latest record/digest/KV version against authenticated OpenBao readback. An older snapshot alone cannot reset the independent high-water record.