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

Schedule 18:00Z custody for acknowledged audit-core E2

Browse source 
Record the owner-acknowledged window, pin the runner invocation including
the forged fixture id, and ask railiance-platform to project identities
only at window start. No mint, no pod apply, no packets.

Assistant: grok
Assistant-Session: 01a02670-3345-76f2-a014-70fde8e2a2bb
This commit is contained in:
tegwick 2026-08-22 12:16:29 +02:00
parent 32afceb68e
commit b8facab717
8 changed files with 139 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

8
SCOPE.md
View file

@ -69,11 +69,9 @@ boundary always holds.
- `T01` is complete: the rules of engagement were accepted on 2026-08-21.
- `T02` is complete: the per-axis attacker model is recorded in
`docs/attacker-model.md`.
- `T03` is in progress: the differential core, audit-core adapter and test
plane admission exist. `tenant-engine` is registered `not_applicable` for
E2. The foundational plane is applied. `WH-ENG-20260822-AUDIT-E2-01` is
operator-approved and awaits target-owner acknowledgement and a connected
custody broker.
- `T03` is in progress: `WH-ENG-20260822-AUDIT-E2-01` is operator-approved
and owner-acknowledged. The window has not started. Custody projection is
scheduled for `18:00Z`; tokens must not be minted early.
- `T04` is complete for every applicable E2 probe: generic and audit-core
shaped fixtures fail known-bad and pass known-good in-process.
- `T05` is in progress: 24-hour cadence, offline evaluator and in-process