Files

T

jschoubben 2d95c0eb59 AM-D3 path: the tool runner states its own fingerprint beside its capabilities

A capability reading must be tied to the runner that made it, so the grants
part can tell an older runner's reading from the running one's.

Builds: design 46 7 §6 (the announcement carries the runner's fingerprint), lead answer A-203 (key `fingerprint`)

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-12 06:02:18 +01:00

cmd/node-tools

A-165 callers: the tool runner refuses a seat verb's caller outside its effective callers before the bundle

2026-11-12 05:49:57 +01:00

internal

AM-D3 path: the tool runner states its own fingerprint beside its capabilities

2026-11-12 06:02:18 +01:00

test/fixtures

Remove the TypeScript runtime code that called the old catalog module's tools; a test finds no file naming one (ADR 0604 section 4, issue 774)

2026-11-03 17:15:17 +01:00

go.mod

A-4 record: a run on the operator's approval answers its approval and is recorded in the hand-act log

2026-11-12 05:18:42 +01:00

go.sum

Require every mesh package of the group at the floor version (ADR 0573 sections 2 and 4, issue 1966)

2026-11-05 16:56:39 +00:00

module.json

E-1: the tool runner's manifest names no waits and keeps its approvals (issue 1966)

2026-11-12 05:00:03 +01:00

package-lock.json

Remove the TypeScript runtime code that called the old catalog module's tools; a test finds no file naming one (ADR 0604 section 4, issue 774)

2026-11-03 17:15:17 +01:00

package.json

Remove the TypeScript runtime code that called the old catalog module's tools; a test finds no file naming one (ADR 0604 section 4, issue 774)

2026-11-03 17:15:17 +01:00

README.md

Name no controller verb in hints and drop its handover and paging reads, since the controller ended (issue 1126 B19)

2026-11-02 11:23:14 +01:00

README.md

node-tools

The node's tool runtime as a module (novox/hq ADR 0175, to-be 38 WP3). Assigned to a machine, it is one process the host runs from this bundle, as the operator's account: it serves every assigned module's tools and every held seat's verbs on the bus, and answers MCP on the machine's loopback — the console (design 34). The mesh composes the process (which bundles to load, where the credential is, whose machine it is); this manifest says only what the machine must have for it: the interpreter, a place for the credential, the loopback port, and leave to call every tool.

The code is the mesh-tools package in this directory; the module at the repository root, mesh-tools, builds the images TypeScript bundles are compiled in. See the repository README.