jochen
c58ce2c7fe
The coming issues module hands out issue numbers from its own state; two instances must never hand out one number twice. Create and Update already write by compare-and-set (ADR 0259), so State(...).Increment reads, writes one more at the revision read, and on a lost write reads and tries again, bounded by the caller's attempts. A lost write past the bound is ErrChanged, any other refusal and a value that is no counter are returned at once: nothing is reported counted that was not written. Part of the issue tracker decision, hq research 042.
mesh-sdk for Go
stdio.Serve("", tools) speaks MCP over stdio to the node's tool runtime, as the module the runtime
names (novox/hq ADR 0188, ADR 0193). A Tool is a name, a description, an argument schema and a
function; calls run concurrently. A tool named <seat>.<verb> is the seat's implementation.
stdio.Emit(type, body) publishes an event as the module, stdio.Subscribe(pattern, handler) receives the module's events (taken when the handler returns nil, offered again when it returns an error — the one rule is in the repository README, "Taking an event") and stdio.Ask(key, body) calls a tool, and stdio.State(name) gets, puts, deletes, lists and watches the module's declared state — all through the runtime (novox/hq ADR 0193, 0198, 0201). Standard library only.
Installing
GOPRIVATE=git.novox.be go get git.novox.be/novox/mesh-sdk/go@latest
Releases are tagged go/vX.Y.Z in this repository, the subdirectory form Go's module system expects,
at the same version as the TypeScript package.
What it holds, under ADR 0039's test: the stdio loop and the tool type, and cli, the local protocol
mesh-cli speaks to the node-engine on its machine (novox/hq ADR 0272): the socket's path and one request and one
answer. Nothing else — no bus, no client, nothing of any module's. go build ./example and pipe a tools/list request into it.