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

Include platform owner in WP-0024 receipts
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-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
This commit is contained in:
codex 2026-08-22 14:59:59 +02:00
parent d8c0cd38a7
commit abf8855ae1
4 changed files with 51 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/wp0024-owner-review-interface.md
View file

@ -20,8 +20,8 @@ python3 scripts/wp0024-owner-review.py verify --owner audit-core
python3 scripts/wp0024-owner-review.py approve --owner audit-core --reviewer audit-core
```
Valid owners are `audit-core`, `rapp-postgres`, `railiance-cluster`, and
`railiance-infra`. `approve` repeats verification and submits the receipt only
Valid owners are `audit-core`, `rapp-postgres`, `railiance-cluster`,
`railiance-infra`, and `railiance-platform`. `approve` repeats verification and submits the receipt only
when artifact hashes and all named read-only checks pass. The checks may read
resource metadata, but they never read Secret data or OpenBao lease payloads.
They cannot revoke a lease, restart a workload, create a snapshot, or reboot a
@ -29,9 +29,9 @@ node. A successful review is still not a live execution window.
The task-to-owner interface is explicit in the contract:
- T02 requires `audit-core` and `rapp-postgres`.
- T02 requires `audit-core`, `rapp-postgres`, and `railiance-platform`.
- T03 requires `audit-core`, `rapp-postgres`, `railiance-cluster`, and
`railiance-infra`.
`railiance-infra`, plus `railiance-platform`.
One owner receipt may approve both tasks when that owner is responsible for
both; its receipt is bound to all artifacts and checks in that owner's review.