novox/hq

Files

T

jochen a28da1734b Graduate research 034: the mesh in domains, one word per thing, checked

ADR 0244 sorts the mesh's concepts into ten domains (ADR 0006's contexts
carry over as domains), keeps machine and node as distinct words, and
makes the glossary the authority with every retired word on its
replacement's Not: line. To-be 49 draws the domains; the glossary is
reorganised by them, its two contradictions removed and the missing
words added. words.py now fails on a retired word in running prose and
on a word defined twice, so the rule is enforced rather than believed;
the 63 documents it failed on are reworded here, and research 034 is
kept as the record of the words it studied.

2026-10-07 19:58:39 +02:00

4.2 KiB

Raw Blame History

layer, status, code, updated, decisions

layer

status

code

updated

decisions

as-is

implemented

mesh-catalog modules/mesh-console

mesh-tools src/mesh.ts

mesh-tools src/http.ts

mesh-tools src/runtime.ts

mesh-controller internal/broker

mesh-controller cmd/mesh-controller/check.go

mesh-controller cmd/mesh-controller/seatverbs.go

2026-09-30

02-DECISIONS/0152-the-operators-surface-is-a-module-the-console.md

02-DECISIONS/0095-the-control-plane-is-the-way-to-ask-a-module.md

02-DECISIONS/0037-where-a-module-lives.md

02-DECISIONS/0154-the-meshs-own-verbs-are-the-controller-seats-tools.md

The mesh MCP server, as it runs

The mesh's tools reach a person through a module the mesh assigned to their machine. Since 2026-09-30 a workstation that is a node can be assigned mesh-console; the mesh mints a bus account <node>.mesh-console, seals its credential to the machine, and the container binds 127.0.0.1:<port> with the port the mesh assigned for the manifest's declared one. An agent on the machine is pointed at http://127.0.0.1:<port>/mcp and sees the mesh's tools; a person uses the same endpoint. Nothing on the machine holds a credential a person had to carry.

What it answers

initialize, tools/list, tools/call, over HTTP, one JSON body per request, no session and no event stream. tools/list is what the running modules answered: every tool runner built on or after that day serves a tools verb for its module, and the mesh MCP server asks the catalogue for the roster and each module for its tools. A module that did not answer is named in the list's _meta.notAnswering. On the day it shipped that was 36 of 51 modules — those that serve no tools at all, and those whose rebuilt runtime the mesh records rather than rolls out — and 62 tools from the rest.

tools/call reaches any tool by <module>.<tool>, listed or not. The mesh MCP server's grant is *, so what it may call is every tool on the mesh; its account may publish nothing else and subscribes nothing.

The mesh's own verbs

Since 2026-09-30 evening (ADR 0154). The mesh MCP server asks the mesh-controller seat's tools verb beside the modules and lists every role's tools as <seat>.<verb> — mesh-controller.status, mesh-controller.push and the other ten. A call to <prefix>.<name> reaches the seat when the prefix is a seat declaring that verb, and the module otherwise; seat:<seat>.<verb> says so outright. When the controller does not answer, the list names mesh-controller (seat) as not answering and carries the modules' tools regardless. The mesh-controller module is always named as not answering: it serves no module tools, only its seat's.

Around it

invokes in a manifest is the grant. It is composed into the bus's user list exactly as a person's account is; the mesh MCP server is the only module that declares it.
module check <file|dir>… on the controller's binary judges a manifest with no mesh: the strict parse, every per-manifest problem, and the rules between the manifests given. It prints what it cannot judge without a store rather than refusing. The mesh MCP server's own manifest was the first thing checked with it, and the whole catalogue passes.
The person's client remains. operator issue and mesh tools|call|mcp with a credential file still work, for a machine that is not a node and for a mesh not yet able to assign anything. mesh tools --console <url> goes through a running mesh MCP server with no credential; it is covered by the runtime repository's tests and was not exercised on the live mesh.

What shipped bent

A module registered by hand from the catalogue with --source <url> --path modules/<m> records a URL, not a place on the git seat: --self takes the forge path form (<owner>/<repository>), which the operator did not pass. The rebuild-on-merge matched the URL anyway.
Modules whose upgrade policy is record — the forge among them — answered tools only once something pushed their rebuilt runtime; until then they are listed as not answering while still callable. That is the policy doing what it says, not a fault of the mesh MCP server.

4.2 KiB Raw Blame History