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

Finish RPF-WP-0019 apps-pg controls and recovery
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source
This commit is contained in:
codex 2026-08-20 22:58:45 +02:00
parent 272c1691c3
commit cb321deeab
16 changed files with 517 additions and 68 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/tenancy-posture.md
View file

@ -180,6 +180,16 @@ Declaring `P: 1` for `apps-pg` would read as though the cluster had a
placement, and a later reader would use it to argue about isolation. `n/a`
plus the provider statement is the accurate canonical form.
For `apps-pg`, the provider statement is now backed by live evidence dated
2026-08-20. A separately restored cluster recovered both consumer databases in
56 seconds from the governed 30-day backup path, establishing current R2/V1
for the provider. The 14-assertion isolation harness then proved own-database
access, cross-database denial, both role timeouts, the 20-connection boundary,
and peer availability while one role exhausted its allowance. The measured
wall-time increase is recorded but is not a latency SLO. Evidence:
`docs/evidence/RPF-WP-0019-backup-restore-2026-08-20.md` and
`docs/evidence/RPF-WP-0019-isolation-2026-08-20.md`.
## Finding adopted by `net-kingdom`
**The six ladders describe a consumer of storage. They do not describe a