coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record archive recovery lifecycle and validate receipt provenance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-06 14:53:15 +02:00
parent 445f1361dc
commit a867ec269a
9 changed files with 203 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

13
workplans/RPF-WP-0036-platform-service-assurance.md
View file

@ -278,3 +278,16 @@ reports 16 healthy, six missing and one stale ESO refresh signal. The aggregate
crossed the one-hour diagnostic boundary; subsequent metadata inspection found
all 27 ExternalSecrets Ready with newer refreshes. Cadence/grace acceptance is
still needed; no outage or successful alert transport is inferred.
## Archive receipt producer repair — 2026-09-06
T03 progressed further: primary/secondary transfer, primary decryption and
isolated restore now emit their own start/finish timestamps, including failures.
Decryption preserves its schema instead of inheriting the transfer's. Restore
checks receipt schema and decryption proof, hashes the exact input receipt and
marks failed cleanup as failed recovery. This closes the producer timestamp gap
for future runs; old evidence remains unchanged. Native adapters remain the only
automatic recovery adapters pending reviewed fresh archive receipts and adapter
implementation. Validation and residual gates are recorded in
`history/2026-09-06-archive-receipt-review.md`; T03 remains waiting on its wider
cadence/custody/acceptance gates.