diff --git a/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md b/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
index 5693f4a..3b7e914 100644
--- a/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
+++ b/workplans/AUDIT-WP-0008-tenancy-posture-alignment.md
@@ -429,6 +429,16 @@ engagement boundary even before registry cleanup completes. The field is
 optional for existing production identities and is preserved across the
 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
 id: AUDIT-WP-0008-T06
 status: done