For hq ADR 0274 (hq #268, proposed) and the operator's ask of 2026-10-10 ("mcp-tools to add mesh-shared instructions/context"). Pairs with mesh-controller #194 (warranted), which should be live before this rolls out.
Tools
claude_code_instructions_propose (scope mesh | node, nodes, name, text, or remove): refuses issue 340's executable content (shell lines, front matter incl. hooks/mcpServers/permissionMode/allowed-tools, @ file refs), secret shapes, >16 KiB, a name the terminal sets, the home scope; refuses at once when no channel kind promises choice + exact-render + verified-sender (names the terminal's line). Keeps the proposal in the new proposals state and publishes one ask under ask.claude-code: Approve and Decline both at level approve, each binding the act digest (proposal id, action, scope, nodes, name, text digest, from, at); expires in a day less 10 min. The phone shows "Add instructions '' to every Claude session on the mesh?", the whole text when ≤2000 bytes/40 lines and every line passes a conservative filter, else the first lines + fingerprint + mesh-cli ask claude-code claude_code_proposals '{"id": ...}'.
claude_code_proposals (id?): proposals, where each stands on this node, the whole text + digest with an id, and the sections approved here.
Activation (every node proves it itself): each instance reads the router's own record of the ask (SeatRecord, router-only writer), composes the ask again from the proposal, holds the warrant to it (Warrant.For: same ask digest, chosen option, level, in time), checks Option.Performs(act) and the text digest, then writes the section to its own approved.json, rendered under "Instructions the operator approved". Decided once per node (replay changes nothing); oldest warrant first. Removal is a proposal approved the same way; a bus record deleted removes nothing. Woken by the decided event, a watch on proposals, and once a minute. The text is never logged.
Manifest: uses: [operator-channel], state proposals, the two tools. SDK bumped to the controller's pseudo-version (asks + SeatRecord).
Tests (proposals_test.go): ask at level approve and nothing active; approval proved on another node renders; decline/expiry/router refusal/changed text (with digest, digest kept, and past what the phone shows)/forged words/late answer/acknowledge level/no person/another ask's warrant all render nothing; once only; removal needs approval; node scope; fail closed (no verified-sender channel; bus refuses the ask); refusals; long text excerpt + whole text via list; text never logged; tools through the real dispatch. go test -race and merge-check.sh (with a locally built controller as MESH_GATE) pass.
For hq ADR 0274 (hq #268, proposed) and the operator's ask of 2026-10-10 ("mcp-tools to add mesh-shared instructions/context"). Pairs with mesh-controller #194 (`warranted`), which should be live before this rolls out.
**Tools**
- `claude_code_instructions_propose` (scope mesh | node, nodes, name, text, or remove): refuses issue 340's executable content (shell lines, front matter incl. hooks/mcpServers/permissionMode/allowed-tools, `@` file refs), secret shapes, >16 KiB, a name the terminal sets, the home scope; refuses at once when no channel kind promises choice + exact-render + verified-sender (names the terminal's line). Keeps the proposal in the new `proposals` state and publishes one ask under `ask.claude-code`: Approve and Decline both at level approve, each binding the act digest (proposal id, action, scope, nodes, name, text digest, from, at); expires in a day less 10 min. The phone shows "Add instructions '<name>' to every Claude session on the mesh?", the whole text when ≤2000 bytes/40 lines and every line passes a conservative filter, else the first lines + fingerprint + `mesh-cli ask claude-code claude_code_proposals '{"id": ...}'`.
- `claude_code_proposals` (id?): proposals, where each stands on this node, the whole text + digest with an id, and the sections approved here.
**Activation (every node proves it itself)**: each instance reads the router's own record of the ask (`SeatRecord`, router-only writer), composes the ask again from the proposal, holds the warrant to it (`Warrant.For`: same ask digest, chosen option, level, in time), checks `Option.Performs(act)` and the text digest, then writes the section to its own `approved.json`, rendered under "Instructions the operator approved". Decided once per node (replay changes nothing); oldest warrant first. Removal is a proposal approved the same way; a bus record deleted removes nothing. Woken by the decided event, a watch on `proposals`, and once a minute. The text is never logged.
**Manifest**: `uses: [operator-channel]`, state `proposals`, the two tools. SDK bumped to the controller's pseudo-version (asks + SeatRecord).
**Tests** (`proposals_test.go`): ask at level approve and nothing active; approval proved on another node renders; decline/expiry/router refusal/changed text (with digest, digest kept, and past what the phone shows)/forged words/late answer/acknowledge level/no person/another ask's warrant all render nothing; once only; removal needs approval; node scope; fail closed (no verified-sender channel; bus refuses the ask); refusals; long text excerpt + whole text via list; text never logged; tools through the real dispatch. `go test -race` and merge-check.sh (with a locally built controller as MESH_GATE) pass.
mesh/merge-gate fail: builds claude-code → ace, g14, novox, shanks; no bus step; a manifest the change touches fails the module check: claude-code uses the…
Shared instructions were the terminal's alone since hq issue 340, because the tool runner cannot tell an
agent from the operator. The operator channel now proves who answered, so an agent may propose a section;
each node proves the router's warrant against the exact text itself and keeps what it approved in its own
file, so nothing written to the bus becomes active.
Deliverynovox/mesh-catalog@e4edab3fd0eb — delivered since 2026-10-10T11:00:12Z
Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
tier 0: claude-code
ace: receives claude-code
g14: receives claude-code
novox: receives claude-code
shanks: receives claude-code
claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Machines
claude-code on ace: passed — healthy 3 times over 2m22s
claude-code on the rest running it: sent
Transitions
2026-10-10 01:56 (new) → proposed (announced): novox/mesh-catalog#170's head announced
2026-10-10 01:56 proposed → checked (checked): the verdict names this commit
2026-10-10 01:56 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-10 10:25 rejected → proposed (recheck): issue 364's fix (mesh-controller #195) is the controller the mesh runs since about 12:25; its red gate was that defect
2026-10-10 10:28 proposed → checked (checked): the verdict names this commit
2026-10-10 10:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 10:56 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-10 10:56 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-10 11:00 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@e4edab3fd0eb` — **delivered** since 2026-10-10T11:00:12Z
**Delivery plan** — builds claude-code → ace, g14, novox, shanks; no bus step
- tier 0: claude-code
- ace: receives claude-code
- g14: receives claude-code
- novox: receives claude-code
- shanks: receives claude-code
- claude-code keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- claude-code on ace: passed — healthy 3 times over 2m22s
- claude-code on the rest running it: sent
**Transitions**
- 2026-10-10 01:56 (new) → proposed (announced): novox/mesh-catalog#170's head announced
- 2026-10-10 01:56 proposed → checked (checked): the verdict names this commit
- 2026-10-10 01:56 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
- 2026-10-10 10:25 rejected → proposed (recheck): issue 364's fix (mesh-controller #195) is the controller the mesh runs since about 12:25; its red gate was that defect
- 2026-10-10 10:28 proposed → checked (checked): the verdict names this commit
- 2026-10-10 10:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 10:56 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-10 10:56 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-10 11:00 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: FAIL — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
tier 0: claude-code
ace: receives claude-code
g14: receives claude-code
novox: receives claude-code
shanks: receives claude-code
claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as build-1791596487266426524 (builds --log build-1791596487266426524).
--- the gate: claude-code
claude-code uses the seat "operator-channel", which no module declares and the mesh does not define
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
mesh-controller: 1 problem(s) in 1 manifest(s)
--- the same manifests on main
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 36715 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 1.931s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `74e1be97`
- `mesh/merge-gate`: **FAIL** — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds claude-code → ace, g14, novox, shanks; no bus step
- tier 0: claude-code
- ace: receives claude-code
- g14: receives claude-code
- novox: receives claude-code
- shanks: receives claude-code
- claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as `build-1791596487266426524` (`builds --log build-1791596487266426524`).
```
--- the gate: claude-code
claude-code uses the seat "operator-channel", which no module declares and the mesh does not define
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
mesh-controller: 1 problem(s) in 1 manifest(s)
--- the same manifests on main
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 36715 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 1.931s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate fail: builds claude-code → ace, g14, novox, shanks; no bus step; a manifest the change touches fails the module check: claude-code uses the…
An @ after any whitespace or punctuation, invisible and control characters, and top headings are refused;
every node judges a proposal record as the module would have made it before applying an approval, never
applies one older than its section's last change, never takes an unreadable record for an empty one, and
keys a node section by its nodes. The controller records the warrant from the router's word alone.
mesh/merge-gate: FAIL — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
tier 0: claude-code
ace: receives claude-code
g14: receives claude-code
novox: receives claude-code
shanks: receives claude-code
claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as build-1791597155820833573 (builds --log build-1791597155820833573).
--- the gate: claude-code
claude-code uses the seat "operator-channel", which no module declares and the mesh does not define
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
mesh-controller: 1 problem(s) in 1 manifest(s)
--- the same manifests on main
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.007s
words: 12 retired words and 70 daemons' lines, none in the 36761 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 3.595s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `490f76e2`
- `mesh/merge-gate`: **FAIL** — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds claude-code → ace, g14, novox, shanks; no bus step
- tier 0: claude-code
- ace: receives claude-code
- g14: receives claude-code
- novox: receives claude-code
- shanks: receives claude-code
- claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as `build-1791597155820833573` (`builds --log build-1791597155820833573`).
```
--- the gate: claude-code
claude-code uses the seat "operator-channel", which no module declares and the mesh does not define
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
mesh-controller: 1 problem(s) in 1 manifest(s)
--- the same manifests on main
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.007s
words: 12 retired words and 70 daemons' lines, none in the 36761 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 3.595s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate pass: builds claude-code → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/merge-gate: FAIL — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
tier 0: claude-code
ace: receives claude-code
g14: receives claude-code
novox: receives claude-code
shanks: receives claude-code
claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on g14 as build-1791597370853785369 (builds --log build-1791597370853785369).
--- the gate: claude-code
claude-code uses the seat "operator-channel", which no module declares and the mesh does not define
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
mesh-controller: 1 problem(s) in 1 manifest(s)
--- the same manifests on main
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 36772 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.004s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 2.039s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `e4edab3f`
- `mesh/merge-gate`: **FAIL** — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds claude-code → ace, g14, novox, shanks; no bus step
- tier 0: claude-code
- ace: receives claude-code
- g14: receives claude-code
- novox: receives claude-code
- shanks: receives claude-code
- claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on g14 as `build-1791597370853785369` (`builds --log build-1791597370853785369`).
```
--- the gate: claude-code
claude-code uses the seat "operator-channel", which no module declares and the mesh does not define
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
mesh-controller: 1 problem(s) in 1 manifest(s)
--- the same manifests on main
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 36772 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.004s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 2.039s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
tier 0: claude-code
ace: receives claude-code
g14: receives claude-code
novox: receives claude-code
shanks: receives claude-code
claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as build-1791627939692230952 (builds --log build-1791627939692230952).
--- the gate: claude-code
note: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T10:17:18Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T10:17:18Z
modules the change moves:
- claude-code (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): claude-code
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.007s
words: 12 retired words and 70 daemons' lines, none in the 36772 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 3.355s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `e4edab3f`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds claude-code → ace, g14, novox, shanks; no bus step
- tier 0: claude-code
- ace: receives claude-code
- g14: receives claude-code
- novox: receives claude-code
- shanks: receives claude-code
- claude-code keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as `build-1791627939692230952` (`builds --log build-1791627939692230952`).
```
--- the gate: claude-code
note: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
claude-code: ok, 43 tool(s), keeps state servers, holdings, config, proposals, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T10:17:18Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T10:17:18Z
modules the change moves:
- claude-code (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): claude-code
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.007s
words: 12 retired words and 70 daemons' lines, none in the 36772 strings of 631 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok claude-code/cmd/claude-code 3.355s
--- its merge-check-typescript.sh (typescript toolchain)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For hq ADR 0274 (hq #268, proposed) and the operator's ask of 2026-10-10 ("mcp-tools to add mesh-shared instructions/context"). Pairs with mesh-controller #194 (
warranted), which should be live before this rolls out.Tools
claude_code_instructions_propose(scope mesh | node, nodes, name, text, or remove): refuses issue 340's executable content (shell lines, front matter incl. hooks/mcpServers/permissionMode/allowed-tools,@file refs), secret shapes, >16 KiB, a name the terminal sets, the home scope; refuses at once when no channel kind promises choice + exact-render + verified-sender (names the terminal's line). Keeps the proposal in the newproposalsstate and publishes one ask underask.claude-code: Approve and Decline both at level approve, each binding the act digest (proposal id, action, scope, nodes, name, text digest, from, at); expires in a day less 10 min. The phone shows "Add instructions '' to every Claude session on the mesh?", the whole text when ≤2000 bytes/40 lines and every line passes a conservative filter, else the first lines + fingerprint +mesh-cli ask claude-code claude_code_proposals '{"id": ...}'.claude_code_proposals(id?): proposals, where each stands on this node, the whole text + digest with an id, and the sections approved here.Activation (every node proves it itself): each instance reads the router's own record of the ask (
SeatRecord, router-only writer), composes the ask again from the proposal, holds the warrant to it (Warrant.For: same ask digest, chosen option, level, in time), checksOption.Performs(act)and the text digest, then writes the section to its ownapproved.json, rendered under "Instructions the operator approved". Decided once per node (replay changes nothing); oldest warrant first. Removal is a proposal approved the same way; a bus record deleted removes nothing. Woken by the decided event, a watch onproposals, and once a minute. The text is never logged.Manifest:
uses: [operator-channel], stateproposals, the two tools. SDK bumped to the controller's pseudo-version (asks + SeatRecord).Tests (
proposals_test.go): ask at level approve and nothing active; approval proved on another node renders; decline/expiry/router refusal/changed text (with digest, digest kept, and past what the phone shows)/forged words/late answer/acknowledge level/no person/another ask's warrant all render nothing; once only; removal needs approval; node scope; fail closed (no verified-sender channel; bus refuses the ask); refusals; long text excerpt + whole text via list; text never logged; tools through the real dispatch.go test -raceand merge-check.sh (with a locally built controller as MESH_GATE) pass.Delivery
novox/mesh-catalog@e4edab3fd0eb— delivered since 2026-10-10T11:00:12ZDelivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
74e1be97mesh/merge-gate: FAIL — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791596487266426524(builds --log build-1791596487266426524).Merge check at
490f76e2mesh/merge-gate: FAIL — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791597155820833573(builds --log build-1791597155820833573).Merge check at
e4edab3fmesh/merge-gate: FAIL — a manifest the change touches fails the module check: claude-code uses the seat "operator-channel", which no module declares and the mesh does not define (modules: claude-code)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791597370853785369(builds --log build-1791597370853785369).Merge check at
e4edab3fmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds claude-code → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791627939692230952(builds --log build-1791627939692230952).