diff --git a/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md b/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
index dfb817f..e0c87f9 100644
--- a/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
+++ b/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
@@ -408,13 +408,18 @@ obligation. This is readiness, not evidence or live authorization. T05 becomes
 cluster plane and value-safe custody broker are provisioned, the bounded run
 completes, and its sanitized target report reaches `risk-nexus`.
 
-Preflight coordination for proposed fresh identifier
-`WH-ENG-20260822-AUDIT-E2-01` is routed to Whitehat
+The target-side ingress policy was applied to railiance01 on 2026-08-22 and its
+namespace plus both pod-label selectors were read back from the API. Preflight
+coordination reserves candidate identifier `WH-ENG-20260822-AUDIT-E2-01` with
+Whitehat
 (`c45151e1-df1a-4306-a70a-83be7875f01c`), `ops-mason`
 (`ddeff394-00b6-474c-b249-3e0f7f9d6059`), and the OpenBao owner
 `railiance-platform` (`10f80080-4c83-42ba-8590-f23c582d9f05`). The candidate
-window is 2026-08-22 18:00–18:15Z. All three requests are preparation-only;
-operator approval and target-owner acknowledgement remain deliberately pending.
+window is 2026-08-22 18:00–18:15Z. Whitehat will issue the new engagement only
+after Mason provisions the empty namespace/network/service-account foundation;
+that apply was authorized without a runner or credential in
+`7e0c1d68-1a68-4345-a845-44bd0dae8373`. Operator approval and target-owner
+acknowledgement remain deliberately pending.
 
 ```task
 id: AUDIT-WP-0008-T06