From 7b5bc1e444cf57ae5d9ba1dac0c0189c0833e278 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 4 Oct 2026 02:48:59 +0200 Subject: [PATCH] Record the owner requirements that keep the live residuals blocked. WHITEHAT-WP-0006 still waits on rapp-postgres, an operator substrate window, and access-engine or a new audit-core engagement. WHITEHAT-WP-0008 still waits on a named live ASM surface, with T-06 on approval-engine. Assistant: grok Assistant-Session: 01a10450-dda4-7253-91a9-b8dccb2f0173 --- SCOPE.md | 8 +++- ...TEHAT-WP-0006-authorized-live-residuals.md | 48 ++++++++++++------- .../WHITEHAT-WP-0008-live-asm-residuals.md | 25 ++++++++-- 3 files changed, 60 insertions(+), 21 deletions(-) diff --git a/SCOPE.md b/SCOPE.md index 20c9818..8632f98 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -69,8 +69,12 @@ boundary always holds. closed. - Finished: `WHITEHAT-WP-0001` through `WHITEHAT-WP-0005` and `WHITEHAT-WP-0007`. Residual live Tenancy Posture evidence is - `WHITEHAT-WP-0006`. Residual live ASM is `WHITEHAT-WP-0008`. Both are - blocked on authorization. + `WHITEHAT-WP-0006`. Residual live ASM is `WHITEHAT-WP-0008`. Both stay + `blocked` after the 2026-10-04 recheck. T01 waits on `rapp-postgres` for + an ordinary runtime identity. T02 waits on an operator substrate window. + T03 waits on `access-engine` or a new `audit-core` engagement ID. Live ASM + waits on a surface owner, with T-06 on `approval-engine` and a consuming + PEP. No packet is authorized. - `WHITEHAT-WP-0007` triaged Gate House ASM T-01…T-10. Live `asm-tNN` registrations remain `pending`. In-process `fixture-asm-t01`…`t10` calibrations exist. That work authorized no live probe. diff --git a/workplans/WHITEHAT-WP-0006-authorized-live-residuals.md b/workplans/WHITEHAT-WP-0006-authorized-live-residuals.md index 0425712..f862690 100644 --- a/workplans/WHITEHAT-WP-0006-authorized-live-residuals.md +++ b/workplans/WHITEHAT-WP-0006-authorized-live-residuals.md @@ -11,7 +11,7 @@ origin_ref: WHITEHAT-WP-0001 owner: net-kingdom topic_slug: whitehat-security created: "2026-09-01" -updated: "2026-09-01" +updated: "2026-10-04" related: - WHITEHAT-WP-0001 state_hub_workstream_id: "fe26f070-70ca-55ba-92b3-3378929ba90f" @@ -45,14 +45,15 @@ status: wait flavor: residual priority: medium state_hub_task_id: "ed82ecb5-e9b9-57e2-a010-5531763f7c4e" +blocked_on: message-from:rapp-postgres +blocking_reason: "rapp-postgres must name a database whose ordinary runtime identity can read the conformance view without BYPASSRLS, superuser, or owner privilege, and a complete engagement must name that database, window, rate ceiling, abort contact, and finding destination." ``` -Blocked until a named database exposes an ordinary runtime identity that can -read the conformance view without `BYPASSRLS`, superuser or owner privilege, -and until a complete engagement record names the database, window, rate -ceiling, abort contact and finding destination. `platform-pg` stays -`not_applicable` until that identity exists. Do not open a database -connection to finish this task. +Blocked on `rapp-postgres`. Rechecked 2026-10-04: `consumers/isolation-probe.yaml` +still names runtime `isolation_probe_app` and migration `isolation_probe_migrate`, +and `scripts/render_consumers.py` still grants `SELECT` on `rls_conformance` to +the migration role only. `platform-pg` stays `not_applicable` until an ordinary +runtime identity exists. Do not open a database connection to finish this task. ### T02 — Live P1/P2 against a bounded substrate window @@ -62,12 +63,13 @@ status: wait flavor: residual priority: medium state_hub_task_id: "f226b8e1-4754-5360-a73f-a607718fc69d" +needs_human: true +blocking_reason: "An operator must approve a substrate window naming the aggressor consumer, allowance, concurrency and resource ceilings, service classes, headroom threshold, and abort thresholds. No repository has published that window." ``` -Blocked until an operator-approved substrate window names the aggressor -consumer, allowance, concurrency/resource ceilings, service classes, headroom -threshold and abort thresholds. `shared-substrate` stays `pending` until that -window exists. Do not generate load to finish this task. +Blocked on an operator record. Rechecked 2026-10-04: no approved substrate +window is in this repository or in `railiance-master`. `shared-substrate` stays +`pending`. Do not generate load to finish this task. ### T03 — Remaining E2 under new engagement IDs @@ -77,16 +79,30 @@ status: wait flavor: residual priority: medium state_hub_task_id: "414a7f68-b838-5ceb-8123-932c56a2b55b" +blocked_on: message-from:access-engine +blocking_reason: "access-engine must confirm a tenant-A identity with no tenant-B authority for the flex-auth target, or audit-core must approve a later run under a new engagement ID. WH-ENG-20260822-AUDIT-E2-01, -02, and -03 stay terminal." ``` -Blocked until either `flex-auth` names a confirmed tenant-A identity with no -tenant-B authority, or a later `audit-core` run is approved under a **new** -engagement ID. `WH-ENG-20260822-AUDIT-E2-01`, `-02` and `-03` are terminal and -must not be reused. `tenant-engine` stays `not_applicable`. Do not send a -packet to finish this task. +Blocked on `access-engine` (the `flex-auth` target; hub slug `access-engine`). +Either that owner confirms the tenant-A identity, or `audit-core` approves a +later run under a new engagement ID. `WH-ENG-20260822-AUDIT-E2-01`, `-02` and +`-03` are terminal and must not be reused. `tenant-engine` stays +`not_applicable`. Do not send a packet to finish this task. ## Sequencing None of these tasks starts without the engagement record and approvals required by the rules of engagement §1 plus plane admission. T01, T02 and T03 are independent. Offline fixture work stays on `WHITEHAT-WP-0001`. + +## Dependencies owned elsewhere — 2026-10-04 + +Nothing local can proceed. The tasks stay `wait` and this plan stays +`blocked`. Whitehat does not edit the owner repositories. + +1. `rapp-postgres` publishes the ordinary runtime identity for T01. The + current isolation-probe template does not. +2. An operator publishes the substrate window for T02. No repository has it. +3. `access-engine` confirms the flex-auth tenant-A identity for T03, or + `audit-core` approves a new engagement ID. The August 22 audit-core IDs + stay terminal. diff --git a/workplans/WHITEHAT-WP-0008-live-asm-residuals.md b/workplans/WHITEHAT-WP-0008-live-asm-residuals.md index 6431027..b729cb0 100644 --- a/workplans/WHITEHAT-WP-0008-live-asm-residuals.md +++ b/workplans/WHITEHAT-WP-0008-live-asm-residuals.md @@ -11,7 +11,7 @@ origin_ref: WHITEHAT-WP-0007 owner: net-kingdom topic_slug: whitehat-security created: "2026-09-02" -updated: "2026-09-02" +updated: "2026-10-04" related: - WHITEHAT-WP-0007 - WHITEHAT-IN-0002 @@ -44,6 +44,8 @@ status: wait flavor: residual priority: medium state_hub_task_id: "1faabcb7-b3d5-5d52-ae73-95d2e3338c5c" +blocked_on: message-from:approval-engine +blocking_reason: "A surface owner must name, for one Canon test_id, the component revision, identities, window, and technique. T-06 still needs approval-engine and a consuming PEP. secrets-engine 4b4d556 is not that surface. One owner return admits only that test_id, and only after a complete engagement and plane admission." ``` Blocked until a target owner names, for a specific Canon `test_id`, the @@ -52,10 +54,27 @@ engagement record plus plane admission exist. `asm-t01`…`asm-t10` stay `pending` until that happens. Do not relabel a pending target to finish this task. Do not send a packet. -T-06 live still needs a named approval-engine and consuming PEP; the -in-process consume client at secrets-engine `4b4d556` is not that surface. +T-06 is the named gap: `approval-engine` plus a consuming PEP. The in-process +consume client at secrets-engine `4b4d556` is not that surface. A return for +one `test_id` does not admit the other nine. Surfaces still pending are in +`targets/asm-t01.json` through `targets/asm-t10.json`. ## Sequencing Nothing starts without the rules of engagement §1 record and plane admission. Offline fixtures stay on `WHITEHAT-WP-0007`. + +## Dependencies owned elsewhere — 2026-10-04 + +This plan stays `blocked` and T01 stays `wait`. No live surface was named on +recheck. Whitehat does not edit the owner repositories and does not infer a +live result from the fixture calibrations. + +`approval-engine` is the T-06 return path recorded on the task. The other +pending surfaces stay with their owners: agent runtime and PEP for T-01, +credential broker and egress for T-02, human and agent sessions for T-03, +policy PEP and policy repository for T-04, service and MCP PEP for T-05, +revocation owner for T-07, `audit-core` for T-08, state owner for T-09, and +credential-lifecycle owner for T-10. `access-engine` is on the decision path +for T-01, T-03, T-04, T-06, T-07, and T-08 and has not named a revision for +any of them.