diff --git a/intakes/intakes.md b/intakes/intakes.md
index 9a38991..8e69c4b 100644
--- a/intakes/intakes.md
+++ b/intakes/intakes.md
@@ -97,6 +97,14 @@ updated: '2026-09-04T21:55:00+02:00'
 state_hub_intake_id: "01a06e68-8c29-7230-b0dc-88f1e374afa4"
 ```
 
+2026-10-09: the parent operator plan is approved (MASON-WP-0005-T03), so this
+lane can be designed once the adapter's deployment identity is known. Nothing
+in fluid-telegram declares one yet (no manifests; FT-WP-0002-T06 delivered only
+`internal/adaptercfg`, whose `LoadToken` reads `bot-token` alone). Asked
+fluid-telegram (message `6d06bd9d`): where the adapter runs (Kubernetes SA with
+ESO, or a host AppRole), whether it needs `redaction-salt` as well as
+`bot-token`, and per-campaign or shared.
+
 ## MASON-IN-0004 — Close the policy-plus-AppRole escalation path in ops-mason-build
 
 ```yaml