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

docs(AUDIT-WP-0008): record expiry rollout gate
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: 01a025c2-407a-7a32-b40a-f37a52f03f62
This commit is contained in:
tegwick 2026-08-22 12:02:27 +02:00
parent fa6665f819
commit c9274d0b3c
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -429,6 +429,16 @@ engagement boundary even before registry cleanup completes. The field is
optional for existing production identities and is preserved across the optional for existing production identities and is preserved across the
non-secret scope overlay. non-secret scope overlay.
The expiry implementation is deployed from `abd22fa` as image
`sha256:c2fe39a0185b99be3fc0cb14d2de69772b8e66e20490097c9d11d90cc39719a6`;
the receiver rolled out 1/1 Ready and returned operational `/readyz`. Formal
owner acknowledgement remains pending because target review found one stale,
undeclared 20260821 forged fixture ID in the new runner. Whitehat was asked in
`a810dae5-110f-4c3b-a4b8-f6763b4242a2` and
`5ffefc2d-a564-4244-8abc-88a5063a92a2` to bind that ID explicitly to the
20260822 engagement and refresh both target and runner digests before any
credential request.
```task ```task
id: AUDIT-WP-0008-T06 id: AUDIT-WP-0008-T06
status: done status: done