9 Commits

Include renames

Author	SHA1	Message	Date
jochen	0292772f58	Give modules the seat traffic and the contract to ask a person and answer on a channel (hq ADR 0259)	2026-10-08 16:34:16 +02:00
jochen	ec80dcfc22	0.1.13: one rule for taking an event, and no handler left by a refused subscribe (hq issue 276) ... A handler takes an event by returning and asks for it again by throwing; any mesh/event answer but an error is taken. Written down in the README where event handling is, with what follows for a handler: throw only when the work was not done, and be safe to run twice. Both SDKs added the handler before asking the runtime and kept it when the runtime refused, so a module that asks again until it is taken (every Go consumer does) ran its handler once per attempt for every event. A refused subscribe now removes its handler; one the Go runtime did not answer in time is kept, since the runtime may have bound it.	2026-10-06 18:14:58 +02:00
jochen	a75add0d59	Module state is hq ADR 0201 after all: the derived-value record moved to 0202 on hq main	2026-10-04 11:02:45 +02:00
jochen	d937c7bc2f	Module state is hq ADR 0202: 0201 landed first for a provider's derivations	2026-10-04 03:44:56 +02:00
jochen	096c5562a4	A module's state through the runtime, in TypeScript and Go (novox/hq ADR 0201) ... state(name) / stdio.State(name): get, put, delete, keys and watch over the runtime's mesh/state verbs. A watch's handler is registered under the id it is asked with, so its current values — which arrive before the watch is answered — and its changes reach it and no other watch.	2026-10-04 02:47:31 +02:00
jochen	81ca305ddd	The Go SDK subscribes and asks through the runtime (hq ADR 0198) ... Subscribe(pattern, handler) asks the runtime for the module's events and answers each mesh/event only after the matching handlers returned nil, so the runtime acknowledges it on the bus then and not before; Ask(key, body) calls a tool as the module. Topic matching is the TypeScript SDK's.	2026-10-03 23:19:54 +02:00
jochen	b95448be60	The Go SDK serves as the module the runtime names, answers calls concurrently, and emits through the runtime (hq ADR 0193) ... What the TypeScript SDK's stdio loop does, in Go: an empty name serves as MESH_SERVED_MODULE; each call runs beside the loop so a tool waiting on the runtime does not deadlock it; Emit asks the runtime (mesh/publish) with the same envelope and headers. README says how to install it and how releases are tagged.	2026-10-03 22:24:16 +02:00
jochen	6a1f3fb51f	Cite ADR 0188, not 0187: the record was renumbered before it merged (0187 is the dead-tracker record)	2026-10-02 21:29:07 +02:00
jochen	78817c949e	A tools bundle speaks MCP over stdio: the loop in TypeScript, and skeleton SDKs for Python, Go, Rust and C (hq ADR 0187) ... The node's runtime launches a tools bundle as a process and speaks MCP over stdio to it, so a tool may be written in any language and the transport stays in the runtime (ADR 0039's refusal, kept). Each SDK is the loop and the tool type and nothing else: `@novox/mesh-sdk/stdio` (serveStdio, and serveRegisteredOverStdio for a bundle that already registers the in-process way), python/, go/, rust/ and c/ beside it, each with an example answering `greet` and the seat verb `node-lamp.on`. Skeletons, by the operator's direction: the bare minimum one bundle per language needs to be built and answer, proven here by each example answering tools/list and tools/call on stdio.	2026-10-02 20:34:19 +02:00