T

jschoubben 201a413f69 broker: split events (mesh.events) from tool RPC (mesh.rpc)

Per ADR 0047: two topic exchanges kept apart, so a '#' subscription on
mesh.events is a clean audit of module/mesh/node events without the
request/reply tool traffic. Header-in-AMQP, persistent messages, per-
consumer durable dead-lettered queues and prefetch are the remaining
alignment to 0047.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

2026-09-03 23:50:56 +02:00

src

broker: split events (mesh.events) from tool RPC (mesh.rpc)

2026-09-03 23:50:56 +02:00

test

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

.gitignore

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

Dockerfile

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

package-lock.json

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

package.json

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

README.md

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

tsconfig.json

mesh-tools — the tool runtime and AMQP broker binding

2026-09-03 23:21:01 +02:00

README.md

mesh-tools

The Novox Mesh tool runtime — the per-node process that makes a module's tools actually serve.

A module ships its tools (built on @novox/mesh-sdk); this runtime is what loads them and puts them on the mesh. It:

connects the mesh broker (novox/hq ADR 0001) — a concrete AMQP implementation of the sdk's Broker contract;
imports the assigned modules' compiled tool entrypoints, each of which registers its tools as it loads;
serves them through the sdk's serveTools harness, answering tools.invoke over the broker.

Everything hard — dispatch, collection, duplicate-name safety — is the sdk's. This is the thin wrapper that binds the broker and loads the modules. Keeping the AMQP client here, out of the sdk, is deliberate: a broker-client change never rebuilds a module (ADR 0044).

Running it

MESH_BROKER_URL     amqp://…              the mesh broker
MESH_TOOL_MODULES   /a/tools/index.js,…   the assigned modules' compiled tool entrypoints

node dist/main.js, or the container (Dockerfile). On a node the host resolves both variables and starts it like any other supervised workload.

Verified

npm test stands up LavinMQ (the mesh's broker) and proves the whole path over real AMQP: the runtime serves a registered tool, a separate connection invokes it by name and gets the result, and an unknown tool is refused over the wire.