diff --git a/workplans/KEY-WP-0013-approval-engine-resource-audience.md b/workplans/KEY-WP-0013-approval-engine-resource-audience.md
index 46169eb..fe8f624 100644
--- a/workplans/KEY-WP-0013-approval-engine-resource-audience.md
+++ b/workplans/KEY-WP-0013-approval-engine-resource-audience.md
@@ -552,3 +552,9 @@ All tasks T01-T07 are `done`; nothing in this plan is waiting, so it is
 (RPF-WP-0035-T05/T06, AUDIT-WP-0009-T09, KEY-WP-0014-T04). The one open
 question recorded above, disabling the unpresented create+approve client, is a
 KeyCape deployment decision to be tracked in a new plan if taken up.
+
+**2026-10-10:** KeyCape proposed the joint disablement sequence that
+railiance-platform asked for on 2026-09-15, to railiance-platform, approval-engine
+and net-kingdom: remove the registration (attended), verify `invalid_client`,
+unbind the env, retire the ESO delivery, then retire custody. The proposal executes
+nothing. Each owner confirms their step and the founder schedules the attended window.