diff --git a/02-DECISIONS/0154-the-meshs-own-verbs-are-the-controller-seats-tools.md b/02-DECISIONS/0154-the-meshs-own-verbs-are-the-controller-seats-tools.md
index 5baaebf..6260251 100644
--- a/02-DECISIONS/0154-the-meshs-own-verbs-are-the-controller-seats-tools.md
+++ b/02-DECISIONS/0154-the-meshs-own-verbs-are-the-controller-seats-tools.md
@@ -94,6 +94,13 @@ itself restarts, and the console says so rather than hiding the modules' tools w
 **A grant of `*` reaches a role's tools; `seat:<seat>.<verb>` grants one.** The console's `*` needed no
 change to reach the mesh's verbs, which is what a grant meaning *every tool* should mean.
 
+> **The mechanism changed — 2026-10-02, by [ADR 0175](0175-one-tool-runtime-per-node-serves-every-modules-tools-on-the-host-side.md).**
+> The seat gains a generic verb beside the named ones: `command`, which takes one command line as the
+> controller's binary takes it and answers what it printed. The named verbs stand and keep their
+> schemas; `command` is the whole binary, added because the operator decided any node may call any
+> tool and a verb per command was the only thing keeping `node account`, `node show` and the rest
+> behind a shell on the control node. Additive within the version, as §"additive" above allows.
+
 ## Consequences
 
 - **The console answers the mesh's own questions.** Issue 147's first paragraph closes: what a node