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

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

@ -7,7 +7,7 @@ repo: railiance-platform
status: blocked
owner: codex
created: "2026-09-05"
updated: "2026-09-05"
updated: "2026-09-06"
state_hub_workstream_id: "ca639c3d-3a87-5fa4-ad13-6f2e014b0c84"
---
@ -249,11 +249,32 @@ Scaleway is the selected primary; Nextcloud is the independent secondary.
Fresh apps-pg recovery from Scaleway passed in 42.64 seconds with expected
consumer databases and limits, production Ready and scratch cleanup complete.
Evidence: `docs/evidence/scaleway-primary-restore-2026-09-06.json`.
T03 now has this fresh physical recovery receipt but still lacks recurring
cadence, the other recovery surfaces and validated evidence adapters.
T03 now has this fresh physical recovery receipt; recurring assurance cadence
and the remaining recovery surfaces are still incomplete.
The source/live coverage inventory `docs/backup-provider-coverage.md` exposes
missing native primary configuration on forgejo-db/net-kingdom-pg/state-hub-db
and no reviewed Scaleway Forgejo archive destination. Track primary coverage
remaining native primary configuration gaps on net-kingdom-pg/state-hub-db.
Forgejo native database recovery and full Scaleway archive recovery have since
passed; independent Nextcloud essentials recovery also passed (WP-0038). Track primary coverage
here with forge/package/storage owners; do not silently claim the Nextcloud
account cutover filled it or weaken WP-0029's separate incident closure.
## Recovery evidence adapter follow-up — 2026-09-06
T03 advanced: capture now consumes hash-pinned apps-pg and forgejo-db native
Scaleway restore receipts through `scripts/recovery_evidence.py`. Completion
timestamps survive every capture; wrong destination, drift, missing/naive/future
times and unsuccessful cleanup cannot become passing samples. Forgejo database
restore is its own signal. Older application archive receipts lack completion
timestamps and remain outside the automatic adapter; essentials evidence never
substitutes for full recovery. Six previous recovery signals still lack adapters
or accepted evidence. Cadence, independent custody and Q2 transport gates remain.
The Forgejo service record now reflects the completed native/full/essentials
proofs while retaining unsupported guarantees and the pending scheduled cutover.
Live adapter verification: `docs/evidence/RPF-WP-0036-assurance-2026-09-06.json`
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.