runtime: serve each tool over mesh.rpc, and an invoke subcommand (ADR 0052) #3

2026-09-04T23:23:56Z

jschoubben commented

2026-09-04 23:23:56 +00:00

Stacked on #2 (events/module-credential). One commit:

RPC replies ride the mesh.rpc exchange (keyed by the caller's reply queue) rather than the default exchange, so a scoped module account can reply with write on mesh.rpc alone — never the default exchange.
Adds an invoke <module> <tool> [json] subcommand, the caller's side of per-key serving.

Together with the SDK's per-key serving (mesh-sdk #2), this is how a module's tools reach the command surface under the module's own scoped account.

Proven in mesh-lab: assigned-plex/sonarr/grafana serve their tools over this; a caller invokes and gets the tool's answer.

Implements novox/hq ADR 0052 (hq PR #20).

https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

Stacked on #2 (events/module-credential). One commit: - RPC replies ride the `mesh.rpc` exchange (keyed by the caller's reply queue) rather than the default exchange, so a scoped module account can reply with write on `mesh.rpc` alone — never the default exchange. - Adds an `invoke <module> <tool> [json]` subcommand, the caller's side of per-key serving. Together with the SDK's per-key serving (mesh-sdk #2), this is how a module's tools reach the command surface under the module's own scoped account. Proven in mesh-lab: assigned-plex/sonarr/grafana serve their tools over this; a caller invokes and gets the tool's answer. Implements novox/hq ADR 0052 (hq PR #20). https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

jschoubben changed target branch from events/module-credential to main

2026-09-05 01:01:49 +00:00

jschoubben added 5 commits 2026-09-05 01:01:49 +00:00

broker: the ADR 0047 wire shape, and the event failure paths f85d1dc303

The AMQP adapter now honours the full contract: events published
persistent with metadata in headers; a durable per-consumer queue
(<node>.<module>.events) with prefetch and a dead-letter exchange
(mesh.events.dead); manual ack for at-least-once.

Failure paths, not just the happy one:
- a confirm channel, so a publish the broker never accepted fails the
  emit rather than vanishing — at-least-once starts at the emitter;
- a handler that keeps failing is requeued once, then dead-lettered
  (poison set aside, never looping);
- an undecodable body is dead-lettered at once — it never decodes on
  redelivery, and must not wedge the queue.

Binding-conformance tests against a disposable broker (a stand-in for the
mesh-hosted broker, ADR 0001): headers on the wire with a pure body, the
redelivery-limit dead-letter, and the poison-body dead-letter.

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

runtime: an emit primitive, so an events test can put a message on the wire 99ce1e1252

'mesh-tools emit <type> [json]' connects, emits one ADR 0047 event (awaiting
the publish confirm), and exits. The serve path already runs a module's
on('#') subscription as an import side effect, so the runtime hosts both an
emitter and the audit-logger consumer.

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

runtime: connect with a sealed credential, scoped, over pinned amqps (ADR 0048) 04a689e008

A module reads its broker credential from MESH_BROKER_FILE — the sealed
{url,fingerprint} the mesh delivered — and connects over amqps pinned to
exactly that certificate. The pin is two-phase (fetch cert, verify, then
trust only it), because Node's checkServerIdentity does not run under
rejectUnauthorized:false, so a naive connect-then-check would already have
sent the password to whoever answered.

A scoped module (assumeExchanges) never declares the exchanges (its account
may not) nor its own queue with a dead-letter (the broker refuses that to a
non-administrator) — the mesh pre-declared the queue, so it passively checks
it, binds and consumes. The RPC reply queue is lazy, and a module that
registered no tools serves none: a pure-events consumer touches only what its
account allows.

Verified end-to-end against a real broker as the scoped account: the audit
logger consumes # and records events, over an account that is not the
broker's own.

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

runtime: take node and module identity from the sealed credential bf5339cec2

The mesh scoped the account to a node and module; the credential now carries
both, so the runtime names its queue and stamps its events as the mesh
authorised without a manifest interpolating a node the vocabulary has no token
for. Verified: with only MESH_BROKER_FILE, the audit logger consumed as
anchor/audit-logger.

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

runtime: RPC replies ride mesh.rpc; an invoke subcommand (ADR 0052) 4558248f16

Replies go through the RPC exchange keyed by the caller's reply-queue name, not
the default exchange — so a serving module's scoped account answers with write
on mesh.rpc alone, never the default exchange (which would let it publish into
any queue). 'mesh-tools invoke <module> <tool> [args]' is the caller's side, the
sibling of emit. Verified against a real broker: a scoped account serves its
tool and is refused another module's serve queue.

jschoubben merged commit b936812f21 into main

2026-09-05 01:02:47 +00:00

jschoubben deleted branch events/tool-serving

2026-09-05 01:02:47 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-tools#3