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

Advance blocked assurance and operator callback work
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:16:49 +02:00
parent a3ca4b708f
commit 445f1361dc
16 changed files with 505 additions and 144 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/service-assurance.md
View file

@ -103,3 +103,15 @@ Source admission checks happen before deployment in the existing apps-pg and
package owner paths; this additional check detects disclosure drift. It does
not apply resources or become a second provisioning engine. Any new consumer
needs an owner entry and a reviewed baseline update, even within free capacity.
## Native recovery receipt adapter
`capture_service_observation.py` loads `assurance/recovery-evidence.json` through
`recovery_evidence.py`. The reviewed SHA-256 pins bind apps-pg and forgejo-db
restore samples to their Scaleway receipts. Original `finished_at` values drive
freshness; recapturing cannot extend their 30-day diagnostic validity. Missing,
changed, invalid or incorrectly scoped receipts yield unavailable samples.
Update pins only after reviewing replacement evidence. Native database recovery
does not attest full application or essentials recovery. Legacy archive receipts
without completion timestamps remain manual evidence; no timestamp is inferred
from file modification time. Automatic cadence and alert delivery remain pending.