Issue 211: a bundle is built before the toolchain it is compiled in; ADR 0192 progressive insight; design 38 WP4b built, WP4c opened

02-DECISIONS/0192-a-tools-bundle-declares-what-it-is-given-and-the-runtime-hands-it-to-that-bundle-alone.md

@@ -30,6 +30,19 @@ runtime calls without one, so every bundle reads the process's four words.
 Without a rule, each of the thirty-one would answer the question its own way, and the runtime's
 process would be the one place where every module's paths meet.
 
+> **Progressive insight — 2026-10-03.** The context above calls the thirty-one remaining containers
+> tool containers handed what a bundle cannot receive. Measured the same day while building this
+> record: nine of them run only tools; three run a main of their own; twenty import, beside their
+> tools, the module's own long-running code — event handlers that subscribe on the bus and
+> provisioners that act on grants — under the module's own bus identity, and some reach their
+> service by a container network name or need a package the image installed. That code is not a
+> tool and is not this record's to move: under
+> [ADR 0188](0188-a-modules-own-code-is-bundles-in-any-language-and-a-tools-bundle-speaks-mcp-to-the-runtime.md)
+> §3 it is a `process` bundle, and how it is given its credential, its words and its reach is the
+> open question of [design 38](../03-DESIGN/01-to-be/38-building-the-operators-machine.md) WP4c.
+> Decision 4 applies to these containers' tools; the containers themselves go when their other
+> code has moved. The decision and its options stand.
+
 ## Considered Options
 
 1. **The bundle declares its environment on its artifact, and the mesh composes it as a