jschoubben ab0f888d67 node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365) ...

Each tool and seat verb is also served on its caller-named subject, kind call
with the caller's bus user last, which the controller grants each user with its
own name alone; the runtime hands the module that caller in the call's _meta,
never from the body. Calls through the runtime (the console and modules'
invokes) ask the caller-named subject first and the old one only when the first
reached nobody: nothing serves it yet, or the bus refused it because the grant
is not delivered yet, which ends the call at once rather than after 30 s. The
old subjects stay served and say no caller for one release (hq issue 464).

2026-10-11 05:19:08 +02:00

..

alive

Say the node tools are there, every minute (hq to-be 45 Phase 1, S11)

2026-10-06 10:06:29 +02:00

announce

Wait for every runtime discovery hears from, and name the ones it misses

2026-10-05 15:36:10 +02:00

bus

node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365)

2026-10-11 05:19:08 +02:00

console

Rank a search the same whatever order discovery heard things in

2026-10-07 20:27:26 +02:00

launch

node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365)

2026-10-11 05:19:08 +02:00

meshtest

Check the tool runtime's own code before it merges, every test on a bus of its own (hq ADR 0237)

2026-10-06 22:04:46 +02:00

runtime

node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365)

2026-10-11 05:19:08 +02:00

wire

node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193)

2026-10-03 21:21:52 +02:00