hq issue 361 (the control-node's agent account is never judged). This PR adds the terminal line node setuid-search <node>, which nox on the control-node runs.
The controller signs a HandOverAsk with no path under SetuidSearchContext (novox-mesh setuid-search v1) and sends it on mesh.node.<node>.ask.setuid-search. The send path is shared with the hand-over (askSigned).
Grants: the node principal may subscribe to its own subject only. A new writers row (a fresh setuid search asked of a machine, to-be 45 §1, hq #265) lets only the controller publish. The golden config is updated.
It is terminal-only, not a verb. A search can never make a machine free wrongly, but each ask throws a walk away. Asked over and over, it would keep a machine unjudged with its disks busy, and the callers of a verb include agents.
Root-free needs no change. The engine (mesh-host #76) puts the search's progress into the account verdict's reason, which root-free already repeats.
Roll this out before mesh-host #76, so the engine's subscription is granted. merge-check.sh passes locally.
hq issue 361 (the control-node's agent account is never judged). This PR adds the terminal line `node setuid-search <node>`, which `nox` on the control-node runs.
- The controller signs a `HandOverAsk` with no path under `SetuidSearchContext` (`novox-mesh setuid-search v1`) and sends it on `mesh.node.<node>.ask.setuid-search`. The send path is shared with the hand-over (`askSigned`).
- Grants: the node principal may subscribe to its own subject only. A new writers row (`a fresh setuid search asked of a machine`, to-be 45 §1, hq #265) lets only the controller publish. The golden config is updated.
- It is terminal-only, not a verb. A search can never make a machine free wrongly, but each ask throws a walk away. Asked over and over, it would keep a machine unjudged with its disks busy, and the callers of a verb include agents.
Root-free needs no change. The engine (mesh-host #76) puts the search's progress into the account verdict's reason, which root-free already repeats.
Roll this out before mesh-host #76, so the engine's subscription is granted. merge-check.sh passes 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…
After the operator removes by hand what the last search found, no apply says so and nothing searched again
until the next day. node setuid-search <node> signs the ask as a hand-over is, under its own context, on a
subject only the node's engine hears and only the controller may publish.
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 3m37s
mesh-controller on the rest running it: sent
build-agent on novox: passed — healthy 3 times over 3m20s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m19s
route-proxy on the rest running it: sent
Transitions
2026-10-09 23:57 (new) → proposed (announced): novox/mesh-controller#191's head announced
2026-10-10 00:03 proposed → checked (checked): the verdict names this commit
2026-10-10 00:03 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 00:06 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 00:06 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 00:21 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@9cef82011797` — **delivered** since 2026-10-10T00:21:36Z
**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 3m37s
- mesh-controller on the rest running it: sent
- build-agent on novox: passed — healthy 3 times over 3m20s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m19s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-09 23:57 (new) → proposed (announced): novox/mesh-controller#191's head announced
- 2026-10-10 00:03 proposed → checked (checked): the verdict names this commit
- 2026-10-10 00:03 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 00:06 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 00:06 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 00:21 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 novox as build-1791590234278060746 (builds --log build-1791590234278060746).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 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-09T23:50:31Z 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-09T23:50:31Z
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 249.304s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.015s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.028s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/route-proxy 1.115s
ok github.com/novox/mesh-controller/internal/artifacts 1.061s
ok github.com/novox/mesh-controller/internal/broker 2.954s
ok github.com/novox/mesh-controller/internal/builder 3.251s
ok github.com/novox/mesh-controller/internal/catalogue 5.578s
ok github.com/novox/mesh-controller/internal/conditions 2.619s
ok github.com/novox/mesh-controller/internal/envfile 1.030s
ok github.com/novox/mesh-controller/internal/facts 1.036s
ok github.com/novox/mesh-controller/internal/identity 5.212s
ok github.com/novox/mesh-controller/internal/inventory 98.898s
ok github.com/novox/mesh-controller/internal/lease 18.279s
ok github.com/novox/mesh-controller/internal/licences 4.869s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.020s
ok github.com/novox/mesh-controller/internal/link 58.512s
ok github.com/novox/mesh-controller/internal/lint 2.324s
ok github.com/novox/mesh-controller/internal/outward 1.049s
ok github.com/novox/mesh-controller/internal/overlay 1.027s
ok github.com/novox/mesh-controller/internal/secrets 1.521s
ok github.com/novox/mesh-controller/internal/store 3.397s
ok github.com/novox/mesh-controller/internal/testbus 1.213s
ok github.com/novox/mesh-controller/internal/token 1.024s
**Merge check** at `9cef8201`
- `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 novox as `build-1791590234278060746` (`builds --log build-1791590234278060746`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 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-09T23:50:31Z 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-09T23:50:31Z
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 249.304s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.015s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.028s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/route-proxy 1.115s
ok github.com/novox/mesh-controller/internal/artifacts 1.061s
ok github.com/novox/mesh-controller/internal/broker 2.954s
ok github.com/novox/mesh-controller/internal/builder 3.251s
ok github.com/novox/mesh-controller/internal/catalogue 5.578s
ok github.com/novox/mesh-controller/internal/conditions 2.619s
ok github.com/novox/mesh-controller/internal/envfile 1.030s
ok github.com/novox/mesh-controller/internal/facts 1.036s
ok github.com/novox/mesh-controller/internal/identity 5.212s
ok github.com/novox/mesh-controller/internal/inventory 98.898s
ok github.com/novox/mesh-controller/internal/lease 18.279s
ok github.com/novox/mesh-controller/internal/licences 4.869s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.020s
ok github.com/novox/mesh-controller/internal/link 58.512s
ok github.com/novox/mesh-controller/internal/lint 2.324s
ok github.com/novox/mesh-controller/internal/outward 1.049s
ok github.com/novox/mesh-controller/internal/overlay 1.027s
ok github.com/novox/mesh-controller/internal/secrets 1.521s
ok github.com/novox/mesh-controller/internal/store 3.397s
ok github.com/novox/mesh-controller/internal/testbus 1.213s
ok github.com/novox/mesh-controller/internal/token 1.024s
```
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.
hq issue 361 (the control-node's agent account is never judged). This PR adds the terminal line
node setuid-search <node>, whichnoxon the control-node runs.HandOverAskwith no path underSetuidSearchContext(novox-mesh setuid-search v1) and sends it onmesh.node.<node>.ask.setuid-search. The send path is shared with the hand-over (askSigned).a fresh setuid search asked of a machine, to-be 45 §1, hq #265) lets only the controller publish. The golden config is updated.Root-free needs no change. The engine (mesh-host #76) puts the search's progress into the account verdict's reason, which root-free already repeats.
Roll this out before mesh-host #76, so the engine's subscription is granted. merge-check.sh passes locally.
Delivery
novox/mesh-controller@9cef82011797— delivered since 2026-10-10T00:21:36ZDelivery 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
9cef8201mesh/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 novox as
build-1791590234278060746(builds --log build-1791590234278060746).