jochen
f6199fafce
node-tools still has a manifest (invokes *, waits, the mcp-endpoint provision) — describe it in prose instead of saying it has none. The TypeScript sources remain on main; only the built artifact is Go. The mesh-controller seat answers 63 verbs as its own runtime, not 60-93 per node (that is node-tools' own node-scoped seat verbs). Prefer reading mesh_overview live over a count that drifts. An as-is document amends nothing — reworded accordingly.
03-DESIGN / 00-as-is
The mesh as it stands. These documents describe what runs, including the parts nobody would choose again — an as-is layer that only records the good decisions is a brochure.
They are written from the implementation and from the operational record, not from intent. Where the two disagree, the implementation wins and the disagreement is stated.
| Document | Covers |
|---|---|
00-overview.md |
The whole in one pass — what a node is, what a module is, how work reaches it |
01-mesh-and-transport.md |
The mesh database, the broker, discovery, and how a call reaches another node |
02-modules-and-manifests.md |
The module, the manifest, and features as the unit of work |
03-provisioning.md |
Declared requirements, provisioners, credentials, and cross-node grants |
04-delivery.md |
Push to running: the three silos, levels, and what a green pipeline proves |
05-runtime-and-installation.md |
The node runtime, its modes, and how a node comes into being |
06-configuration-and-secrets.md |
Managed files, value resolution, and where secrets live |
07-knowledge.md |
The mesh keeps no store: what it knows is what modules answer, and the record is read by one |
08-agents-and-work.md |
Agents as employees, tasks, workflows, and the meeting model |
09-interfaces-and-observability.md |
How the mesh is reached and watched — tools, board, proxy, health, thoughts |
10-module-catalogue.md |
The catalogue's shape, and what its shape says |
11-the-lab.md |
The lab — the first piece of the new shape that exists, and what it does not yet do |
12-the-seats.md |
The seats the mesh defines, who holds one, and where a seat changes resolution |
13-the-console.md |
The mesh's tools on the machine a person sits at, served by a module the mesh assigned there |
14-a-modules-state.md |
A module's current state on the bus: what the controller creates, the runtime serves, and the first live use showed |
15-the-agent-and-its-licences.md |
The operator's agent on every machine and the licence manager that keeps its licences |
16-logins-on-the-bus.md |
The bus's one list of logins, a login per module assignment, persons limited to their tools, sessions calling through the tool runner's login, and no effect on any tool |
17-accounts-on-a-machine.md |
The operator and agent accounts on the node record, claude-code's own login and guard, the judgement that the agent account cannot become root, and the forge accounts agents push as |
What these documents are not
They are not a runbook. Operational procedure — how to fix one occurrence of something — lives in the knowledge base, which is indexed on symptoms and is the right place to search when something is broken.
They are not exhaustive. A subsystem is described to the depth at which its design is visible; below that is code.