For hq ADR 0274 (hq #268, proposed): the claude-code module (mesh-catalog #170) asks the operator to approve a shared instruction section and acts on the warrant on every node. The hand-act log is where a person's decisions are read back, so this adds the verb warranted (hand-act warrant --asker <module> --ask <id>).
Everything recorded is read from the router's own record of that asker's ask (direct get on the asks seat's records bucket; the controller's grant already reaches $JS.API.>): who chose, via which channel, the proofs, the answer. The caller names the ask and nothing else: a word of its own, recorded first under the one id, would stand for every node's (review of 2026-10-10); what is refused.
Recorded once per ask under warrant-<asker>-<ask> (link.RecordHandActOnce, a KV create), however many instances ask.
Refused: an ask still open, ended without a person's choice, another asker's or another ask's record, the controller's own asks, a warrant naming no ask digest.
Verb warrant is already counted as a person's decision, not a repair; the verb's line is not a repairing command and not terminal-only.
No broker grant change: the module side needs only uses: [operator-channel], which the existing by-caller composition (ADR 0259 §3) turns into publish ask.claude-code, subscribe decided.claude-code and its own records. (The gate refusing that uses is hq issue 364, fixed in mesh-controller #195.)
Tests: warranted_test.go, TestNatsAnActRecordedOnceIsWrittenOnce against a real bus; full go test ./... and go vet ./... pass locally.
For hq ADR 0274 (hq #268, proposed): the claude-code module (mesh-catalog #170) asks the operator to approve a shared instruction section and acts on the warrant on every node. The hand-act log is where a person's decisions are read back, so this adds the verb `warranted` (`hand-act warrant --asker <module> --ask <id>`).
- Everything recorded is read from the router's own record of that asker's ask (direct get on the asks seat's records bucket; the controller's grant already reaches `$JS.API.>`): who chose, via which channel, the proofs, the answer. The caller names the ask and nothing else: a word of its own, recorded first under the one id, would stand for every node's (review of 2026-10-10); `what` is refused.
- Recorded once per ask under `warrant-<asker>-<ask>` (`link.RecordHandActOnce`, a KV create), however many instances ask.
- Refused: an ask still open, ended without a person's choice, another asker's or another ask's record, the controller's own asks, a warrant naming no ask digest.
- Verb `warrant` is already counted as a person's decision, not a repair; the verb's line is not a repairing command and not terminal-only.
- No broker grant change: the module side needs only `uses: [operator-channel]`, which the existing by-caller composition (ADR 0259 §3) turns into publish `ask.claude-code`, subscribe `decided.claude-code` and its own records. (The gate refusing that `uses` is hq issue 364, fixed in mesh-controller #195.)
Tests: `warranted_test.go`, `TestNatsAnActRecordedOnceIsWrittenOnce` against a real bus; full `go test ./...` and `go vet ./...` pass locally.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
A module that asks the operator acts with its own grants, and the hand-act log is where a person's
decisions are read back. The new verb warranted records who chose, how and with which proofs from the
router's record, never the caller's word, once per ask however many instances ask.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m38s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m24s
build-agent on the rest running it: sent
Transitions
2026-10-10 01:56 (new) → proposed (announced): novox/mesh-controller#194's head announced
2026-10-10 02:02 proposed → checked (checked): the verdict names this commit
2026-10-10 02:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 10:40 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:40 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 10:49 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-controller@88e84a4dd783` — **delivered** since 2026-10-10T10:49:16Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m38s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m24s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-10 01:56 (new) → proposed (announced): novox/mesh-controller#194's head announced
- 2026-10-10 02:02 proposed → checked (checked): the verdict names this commit
- 2026-10-10 02:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 10:40 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:40 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 10:49 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`.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on g14 as build-1791596489028664158 (builds --log build-1791596489028664158).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
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-10T01:36:53Z 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-10T01:36:53Z
modules the change moves:
- mesh-controller (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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.041s
ok github.com/novox/mesh-controller/cmd/mesh-controller 213.500s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/route-proxy 1.183s
ok github.com/novox/mesh-controller/internal/artifacts 1.038s
ok github.com/novox/mesh-controller/internal/broker 2.557s
ok github.com/novox/mesh-controller/internal/builder 1.792s
ok github.com/novox/mesh-controller/internal/catalogue 4.383s
ok github.com/novox/mesh-controller/internal/conditions 2.351s
ok github.com/novox/mesh-controller/internal/envfile 1.027s
ok github.com/novox/mesh-controller/internal/facts 1.028s
ok github.com/novox/mesh-controller/internal/identity 3.990s
ok github.com/novox/mesh-controller/internal/inventory 72.359s
ok github.com/novox/mesh-controller/internal/lease 17.600s
ok github.com/novox/mesh-controller/internal/licences 3.584s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 51.957s
ok github.com/novox/mesh-controller/internal/lint 1.925s
ok github.com/novox/mesh-controller/internal/outward 1.030s
ok github.com/novox/mesh-controller/internal/overlay 1.020s
ok github.com/novox/mesh-controller/internal/secrets 1.400s
ok github.com/novox/mesh-controller/internal/store 3.169s
ok github.com/novox/mesh-controller/internal/testbus 1.162s
ok github.com/novox/mesh-controller/internal/token 1.010s
**Merge check** at `0e5aed12`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on g14 as `build-1791596489028664158` (`builds --log build-1791596489028664158`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
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-10T01:36:53Z 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-10T01:36:53Z
modules the change moves:
- mesh-controller (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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.041s
ok github.com/novox/mesh-controller/cmd/mesh-controller 213.500s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/route-proxy 1.183s
ok github.com/novox/mesh-controller/internal/artifacts 1.038s
ok github.com/novox/mesh-controller/internal/broker 2.557s
ok github.com/novox/mesh-controller/internal/builder 1.792s
ok github.com/novox/mesh-controller/internal/catalogue 4.383s
ok github.com/novox/mesh-controller/internal/conditions 2.351s
ok github.com/novox/mesh-controller/internal/envfile 1.027s
ok github.com/novox/mesh-controller/internal/facts 1.028s
ok github.com/novox/mesh-controller/internal/identity 3.990s
ok github.com/novox/mesh-controller/internal/inventory 72.359s
ok github.com/novox/mesh-controller/internal/lease 17.600s
ok github.com/novox/mesh-controller/internal/licences 3.584s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 51.957s
ok github.com/novox/mesh-controller/internal/lint 1.925s
ok github.com/novox/mesh-controller/internal/outward 1.030s
ok github.com/novox/mesh-controller/internal/overlay 1.020s
ok github.com/novox/mesh-controller/internal/secrets 1.400s
ok github.com/novox/mesh-controller/internal/store 3.169s
ok github.com/novox/mesh-controller/internal/testbus 1.162s
ok github.com/novox/mesh-controller/internal/token 1.010s
```
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as build-1791597156369326119 (builds --log build-1791597156369326119).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
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-10T01:45:53Z 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-10T01:45:53Z
modules the change moves:
- mesh-controller (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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 217.768s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.031s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.068s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.207s
ok github.com/novox/mesh-controller/internal/artifacts 1.086s
ok github.com/novox/mesh-controller/internal/broker 2.806s
ok github.com/novox/mesh-controller/internal/builder 1.971s
ok github.com/novox/mesh-controller/internal/catalogue 5.143s
ok github.com/novox/mesh-controller/internal/conditions 2.623s
ok github.com/novox/mesh-controller/internal/envfile 1.044s
ok github.com/novox/mesh-controller/internal/facts 1.068s
ok github.com/novox/mesh-controller/internal/identity 4.813s
ok github.com/novox/mesh-controller/internal/inventory 86.601s
ok github.com/novox/mesh-controller/internal/lease 17.722s
ok github.com/novox/mesh-controller/internal/licences 4.378s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.053s
ok github.com/novox/mesh-controller/internal/link 53.749s
ok github.com/novox/mesh-controller/internal/lint 2.310s
ok github.com/novox/mesh-controller/internal/outward 1.095s
ok github.com/novox/mesh-controller/internal/overlay 1.075s
ok github.com/novox/mesh-controller/internal/secrets 1.592s
ok github.com/novox/mesh-controller/internal/store 3.500s
ok github.com/novox/mesh-controller/internal/testbus 1.253s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `abd30784`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as `build-1791597156369326119` (`builds --log build-1791597156369326119`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
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-10T01:45:53Z 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-10T01:45:53Z
modules the change moves:
- mesh-controller (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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 217.768s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.031s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.068s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.207s
ok github.com/novox/mesh-controller/internal/artifacts 1.086s
ok github.com/novox/mesh-controller/internal/broker 2.806s
ok github.com/novox/mesh-controller/internal/builder 1.971s
ok github.com/novox/mesh-controller/internal/catalogue 5.143s
ok github.com/novox/mesh-controller/internal/conditions 2.623s
ok github.com/novox/mesh-controller/internal/envfile 1.044s
ok github.com/novox/mesh-controller/internal/facts 1.068s
ok github.com/novox/mesh-controller/internal/identity 4.813s
ok github.com/novox/mesh-controller/internal/inventory 86.601s
ok github.com/novox/mesh-controller/internal/lease 17.722s
ok github.com/novox/mesh-controller/internal/licences 4.378s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.053s
ok github.com/novox/mesh-controller/internal/link 53.749s
ok github.com/novox/mesh-controller/internal/lint 2.310s
ok github.com/novox/mesh-controller/internal/outward 1.095s
ok github.com/novox/mesh-controller/internal/overlay 1.075s
ok github.com/novox/mesh-controller/internal/secrets 1.592s
ok github.com/novox/mesh-controller/internal/store 3.500s
ok github.com/novox/mesh-controller/internal/testbus 1.253s
ok github.com/novox/mesh-controller/internal/token 1.015s
```
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on g14 as build-1791597371505284767 (builds --log build-1791597371505284767).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
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-10T01:55:53Z 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-10T01:55:53Z
modules the change moves:
- mesh-controller (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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.048s
ok github.com/novox/mesh-controller/cmd/mesh-controller 207.787s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.015s
ok github.com/novox/mesh-controller/examples/route-proxy 1.192s
ok github.com/novox/mesh-controller/internal/artifacts 1.047s
ok github.com/novox/mesh-controller/internal/broker 2.527s
ok github.com/novox/mesh-controller/internal/builder 1.773s
ok github.com/novox/mesh-controller/internal/catalogue 4.272s
ok github.com/novox/mesh-controller/internal/conditions 2.341s
ok github.com/novox/mesh-controller/internal/envfile 1.029s
ok github.com/novox/mesh-controller/internal/facts 1.034s
ok github.com/novox/mesh-controller/internal/identity 3.983s
ok github.com/novox/mesh-controller/internal/inventory 70.119s
ok github.com/novox/mesh-controller/internal/lease 17.688s
ok github.com/novox/mesh-controller/internal/licences 3.576s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.006s
ok github.com/novox/mesh-controller/internal/link 50.915s
ok github.com/novox/mesh-controller/internal/lint 1.918s
ok github.com/novox/mesh-controller/internal/outward 1.038s
ok github.com/novox/mesh-controller/internal/overlay 1.023s
ok github.com/novox/mesh-controller/internal/secrets 1.383s
ok github.com/novox/mesh-controller/internal/store 3.161s
ok github.com/novox/mesh-controller/internal/testbus 1.164s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `88e84a4d`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on g14 as `build-1791597371505284767` (`builds --log build-1791597371505284767`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
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-10T01:55:53Z 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-10T01:55:53Z
modules the change moves:
- mesh-controller (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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.048s
ok github.com/novox/mesh-controller/cmd/mesh-controller 207.787s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.015s
ok github.com/novox/mesh-controller/examples/route-proxy 1.192s
ok github.com/novox/mesh-controller/internal/artifacts 1.047s
ok github.com/novox/mesh-controller/internal/broker 2.527s
ok github.com/novox/mesh-controller/internal/builder 1.773s
ok github.com/novox/mesh-controller/internal/catalogue 4.272s
ok github.com/novox/mesh-controller/internal/conditions 2.341s
ok github.com/novox/mesh-controller/internal/envfile 1.029s
ok github.com/novox/mesh-controller/internal/facts 1.034s
ok github.com/novox/mesh-controller/internal/identity 3.983s
ok github.com/novox/mesh-controller/internal/inventory 70.119s
ok github.com/novox/mesh-controller/internal/lease 17.688s
ok github.com/novox/mesh-controller/internal/licences 3.576s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.006s
ok github.com/novox/mesh-controller/internal/link 50.915s
ok github.com/novox/mesh-controller/internal/lint 1.918s
ok github.com/novox/mesh-controller/internal/outward 1.038s
ok github.com/novox/mesh-controller/internal/overlay 1.023s
ok github.com/novox/mesh-controller/internal/secrets 1.383s
ok github.com/novox/mesh-controller/internal/store 3.161s
ok github.com/novox/mesh-controller/internal/testbus 1.164s
ok github.com/novox/mesh-controller/internal/token 1.015s
```
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): the claude-code module (mesh-catalog #170) asks the operator to approve a shared instruction section and acts on the warrant on every node. The hand-act log is where a person's decisions are read back, so this adds the verb
warranted(hand-act warrant --asker <module> --ask <id>).$JS.API.>): who chose, via which channel, the proofs, the answer. The caller names the ask and nothing else: a word of its own, recorded first under the one id, would stand for every node's (review of 2026-10-10);whatis refused.warrant-<asker>-<ask>(link.RecordHandActOnce, a KV create), however many instances ask.warrantis already counted as a person's decision, not a repair; the verb's line is not a repairing command and not terminal-only.uses: [operator-channel], which the existing by-caller composition (ADR 0259 §3) turns into publishask.claude-code, subscribedecided.claude-codeand its own records. (The gate refusing thatusesis hq issue 364, fixed in mesh-controller #195.)Tests:
warranted_test.go,TestNatsAnActRecordedOnceIsWrittenOnceagainst a real bus; fullgo test ./...andgo vet ./...pass locally.Delivery
novox/mesh-controller@88e84a4dd783— delivered since 2026-10-10T10:49:16ZDelivery plan — builds build-agent, mesh-controller, route-proxy → 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
0e5aed12mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791596489028664158(builds --log build-1791596489028664158).Merge check at
abd30784mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791597156369326119(builds --log build-1791597156369326119).Merge check at
88e84a4dmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791597371505284767(builds --log build-1791597371505284767).