ADR 0095: the control plane is the way to ask a module; issue 049 resolved; design 19 amended

03-DESIGN/01-to-be/19-the-module-protocol.md

@@ -5,8 +5,9 @@ code:
   - mesh-sdk src
   - mesh-tools src/broker-amqp.ts
   - mesh-controller internal/link
-updated: 2026-09-15
+updated: 2026-09-21
 decisions:
+  - 02-DECISIONS/0095-the-control-plane-is-the-way-to-ask-a-module.md
   - 02-DECISIONS/0074-the-wire-is-specified-not-the-types.md
   - 02-DECISIONS/0039-what-the-sdk-holds-and-refuses.md
   - 02-DECISIONS/0043-a-module-broker-account-is-scoped-by-emits-and-consumes.md
@@ -137,13 +138,15 @@ A module's tools are its operator-facing surface.
   into any queue on the broker.
 - A caller needs a **reply queue**, and that is what a module's scoped account may not declare
   ([issue 049](../../04-ISSUES/049-a-module-can-serve-tools-and-nothing-can-call-them/00-report.md)).
-  So a module may serve tools and may not call them, and nothing today issues an account to anything
-  that wants to ask.
-
-### Not yet true
-
-The caller's half has no account. Until that is settled, the only thing that can ask a module a
-question is the foundation's bootstrap admin, which is not a protocol so much as a way in.
+  So a module may serve tools and may not call them.
+- **The control plane is the way to ask**
+  ([ADR 0095](../../02-DECISIONS/0095-the-control-plane-is-the-way-to-ask-a-module.md)):
+  `ask <module> <tool> [json]` publishes on `mesh.rpc` under `<module>.<tool>` with a private reply
+  queue bound under its own name, and prints the answer as the module gave it. A module declares
+  nothing about being asked — serving a tool is being askable through the control plane. A
+  module-to-module call, if one is wanted, is a grant like any other and a later decision.
+  *How it is checked:* a tools-only bed asks a served tool through the control plane and asserts
+  an answer arrived, where a timeout would read differently.
 
 ---