diff --git a/workplans/WARDEN-WP-0044-security-case-follow-through.md b/workplans/WARDEN-WP-0044-security-case-follow-through.md
index 103446a..75fa494 100644
--- a/workplans/WARDEN-WP-0044-security-case-follow-through.md
+++ b/workplans/WARDEN-WP-0044-security-case-follow-through.md
@@ -168,6 +168,15 @@ Agreed with railiance-platform (RPF-WP-0054-T01, 2026-10-09):
   client_id.
 - warden refuses that step when `WARDEN_AGENT_ID` is set.
 
+2026-10-10: railiance-platform implemented the command (RPF-WP-0054-T03). It is
+catalogued as draft `keycape-client-secret-generate`, with `exec_owner`
+railiance-platform and `exec_capable: false`. `warden case check-type` now
+reports the lane as LANE-UNREVIEWED rather than LANE-MISSING. Before it can be
+activated:
+- the founder binds the issuer policy to the operator OIDC role
+- key-cape confirms the secret format
+- the RPF-WP-0054-T05 probe passes
+
 ```task
 id: WARDEN-WP-0044-T04
 status: wait