diff --git a/04-ISSUES/147-the-operators-tools-still-dial-the-bus-that-was-removed/00-report.md b/04-ISSUES/147-the-operators-tools-still-dial-the-bus-that-was-removed/00-report.md index f4e2d57..b056a21 100644 --- a/04-ISSUES/147-the-operators-tools-still-dial-the-bus-that-was-removed/00-report.md +++ b/04-ISSUES/147-the-operators-tools-still-dial-the-bus-that-was-removed/00-report.md @@ -1,7 +1,7 @@ --- -status: open +status: located opened: 2026-09-29 -located-in: [] +located-in: [nothing in the mesh — the surface in use is the predecessor's, installed on the workstation] --- # 147 — the operator's tools still dial the bus that was removed @@ -49,6 +49,23 @@ reason, which is why lessons from the last two days were written into this repos a person can ask it anything ([issue 145](../145-a-machine-reads-healthy-while-its-modules-cannot-reach-each-other/00-report.md), the same shape one level out). +## Diagnosed at once, because the answer was in the configuration + +**The surface is not the mesh's.** The tool server the operator's assistant speaks to is the +predecessor's brain, installed on the workstation and started as a local process, with the +predecessor's broker URL — `amqp://…@` — written into the assistant's own +configuration. Nothing about it is a module: it has no manifest, no assignment, no seat, no account +on the mesh's bus, and the mesh has never known it exists. + +So nothing regressed. The mesh removed a transport that this program still dials, and the program +was never part of the mesh to be moved. **The mesh has a tool model** — `tools` in a manifest, the +calls a seat accepts, the subjects a module answers on, and a control-plane command that asks one — +and **nothing publishes an operator-facing surface onto it.** What an operator uses is the thing +that came before, kept alive by a URL in a file. + +That is the issue, and it is larger than a broken connection: the way a person drives this mesh is +outside the mesh. + ## Evidence to carry into diagnosis - The failure text names `hal/mesh@`, so the bridge is resolving a node and then dialling the