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

2026-09-21 20:38:23 +02:00
parent acc9824949
commit 39a01b7f7e
5 changed files with 79 additions and 14 deletions
@@ -1,9 +1,9 @@
 ---
-status: located
+status: resolved
 opened: 2026-09-14
-located-in: [mesh-controller cmd/mesh-controller, mesh-tools (the request contract)]
-fixed-by:
-amended-design:
+located-in: [mesh-controller cmd/mesh-controller (ask), mesh-controller internal/link]
+fixed-by: ADR 0095; mesh-controller multiple-fixes (ask: the control plane publishes the request with a private reply queue and prints the answer); proven by the confluence bed
+amended-design: 03-DESIGN/01-to-be/19-the-module-protocol.md
 ---

 # 049 — A module can serve tools, and nothing is allowed to call them
@@ -14,5 +14,6 @@
   like any other, and a later decision.

 **Located in:** the controller (a command speaking the tool request/reply over its own connection)
-and the tool runtime's request contract. Not fixed here: it is a new command against a protocol
-the runtime owns, and needs a lab run against a tools-only bed to be proven.
+and the tool runtime's request contract. Fixed as
+[ADR 0095](../../02-DECISIONS/0095-the-control-plane-is-the-way-to-ask-a-module.md): `ask`,
+proven by the confluence bed asking a served tool and getting its answer.