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

docs(AUDIT-WP-0008): advance live exercise gates
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: 01a02991-be07-7bb3-8b6d-e9701b5621de
This commit is contained in:
tegwick 2026-08-22 15:24:30 +02:00
parent 3758391791
commit d2bba6646d
1 changed files with 25 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

25
workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
View file

@ -448,6 +448,13 @@ no runner pod has been applied, and the pre-window engagement gate still fails
closed. This is readiness evidence only; T05 remains in progress until the
bounded run and sanitized report complete.
A fresh 2026-08-22T13:20Z value-safe preflight still observed no engagement KV
paths, projection resources, or temporary identities; audit-core remained on
the reviewed digest and 1/1 Ready. Whitehat's own engagement validator returned
`engagement window has not started`. The independent custody and engagement
gates therefore agree before the attended window, with no live resource to
clean up early.
```task
id: AUDIT-WP-0008-T06
status: done
@ -519,6 +526,24 @@ read-only preflights passed. Both preflights remain
`ready_for_live_execution: false`: this approves the procedure only and does
not authorize a lease revocation, restart, or reboot window.
Rapp-postgres confirmed its final procedure approval in message
`f9d4606b-56d8-4476-b3ba-166f07e8b527` and fixed the sequencing boundary: no
recovery exercise overlaps the Whitehat E2 window, and the earliest candidate
is after its attended cleanup at 18:15Z. T02 now has all three required
procedure-owner approvals. A 2026-08-22T13:20Z live, read-only preflight passed
all automated checks but remained closed on the synthetic-load contract,
approved window, named abort operator, and runtime acknowledgement fields.
Audit-core requested those remaining gates from `user-engine` and
`railiance-platform` in messages `3a99ec1e-897c-4b29-bdc8-a312c8e990e1` and
`852a7efa-4d25-4d85-a56d-6afed8bc600a`.
T03's automated node-reboot checks also remained clean and value-safe, including
fresh Barman backup and continuous archiving, while correctly refusing live
readiness without snapshot, console, Shamir quorum, window, abort operator, and
complete owner evidence. `railiance-cluster` is the sole missing procedure
owner and received the direct hash-bound review request in
`e13f90f1-0734-4160-aad7-7bba2da29275`. No live recovery action is scheduled.
```task
id: AUDIT-WP-0008-T08
status: done