hq issue 364 (hq #269). The gate runs module check over the touched manifests only, so claude-code (mesh-catalog #170) adding uses: [operator-channel] is refused: the router's declaration is not in the set. The command's documentation already says such a seat is a note.
builder: the gate's module check runs with MESH_MODULE_CHECK_SOME=1.
module check: with that variable, a uses/claim of a seat none of the given manifests declares is printed as a note and not counted; without it (the catalogue's merge-check over every manifest, registration) it stays a refusal.
Skew-safe: a judge that predates the variable ignores it and refuses as before; the fix takes effect once this controller is the one the mesh runs (the judge is built from the running controller's source).
Test: TestASeatAnotherModuleDeclaresIsANoteOverSomeManifests. Full go vet ./... and go test ./... pass locally.
mesh-catalog #170's gate stays red until this is merged and delivered.
hq issue 364 (hq #269). The gate runs `module check` over the touched manifests only, so `claude-code` (mesh-catalog #170) adding `uses: [operator-channel]` is refused: the router's declaration is not in the set. The command's documentation already says such a seat is a note.
- builder: the gate's module check runs with `MESH_MODULE_CHECK_SOME=1`.
- module check: with that variable, a `uses`/claim of a seat none of the given manifests declares is printed as a note and not counted; without it (the catalogue's merge-check over every manifest, registration) it stays a refusal.
- Skew-safe: a judge that predates the variable ignores it and refuses as before; the fix takes effect once this controller is the one the mesh runs (the judge is built from the running controller's source).
Test: `TestASeatAnotherModuleDeclaresIsANoteOverSomeManifests`. Full `go vet ./...` and `go test ./...` pass locally.
mesh-catalog #170's gate stays red until this is merged and delivered.
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…
The gate passes only the manifests a change touches, so a module that starts using the operator channel
was refused for a declaration it could not see. Over every manifest it stays a refusal.
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 3m35s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m28s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m29s
route-proxy on the rest running it: sent
Transitions
2026-10-10 01:54 (new) → proposed (announced): novox/mesh-controller#195's head announced
2026-10-10 01:59 proposed → checked (checked): the verdict names this commit
2026-10-10 01:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 10: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 10: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 10: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@7b5c063cd377` — **delivered** since 2026-10-10T10:21:40Z
**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 3m35s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m28s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m29s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-10 01:54 (new) → proposed (announced): novox/mesh-controller#195's head announced
- 2026-10-10 01:59 proposed → checked (checked): the verdict names this commit
- 2026-10-10 01:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 10: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 10: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 10: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 ace as build-1791597249170720305 (builds --log build-1791597249170720305).
--- 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-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.031s
ok github.com/novox/mesh-controller/cmd/mesh-controller 190.588s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.033s
ok github.com/novox/mesh-controller/examples/route-proxy 1.136s
ok github.com/novox/mesh-controller/internal/artifacts 1.066s
ok github.com/novox/mesh-controller/internal/broker 2.608s
ok github.com/novox/mesh-controller/internal/builder 1.826s
ok github.com/novox/mesh-controller/internal/catalogue 4.390s
ok github.com/novox/mesh-controller/internal/conditions 2.430s
ok github.com/novox/mesh-controller/internal/envfile 1.038s
ok github.com/novox/mesh-controller/internal/facts 1.038s
ok github.com/novox/mesh-controller/internal/identity 4.127s
ok github.com/novox/mesh-controller/internal/inventory 72.019s
ok github.com/novox/mesh-controller/internal/lease 17.670s
ok github.com/novox/mesh-controller/internal/licences 3.699s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.047s
ok github.com/novox/mesh-controller/internal/link 50.994s
ok github.com/novox/mesh-controller/internal/lint 2.014s
ok github.com/novox/mesh-controller/internal/outward 1.060s
ok github.com/novox/mesh-controller/internal/overlay 1.051s
ok github.com/novox/mesh-controller/internal/secrets 1.409s
ok github.com/novox/mesh-controller/internal/store 3.280s
ok github.com/novox/mesh-controller/internal/testbus 1.205s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `7b5c063c`
- `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 ace as `build-1791597249170720305` (`builds --log build-1791597249170720305`).
```
--- 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-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.031s
ok github.com/novox/mesh-controller/cmd/mesh-controller 190.588s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.033s
ok github.com/novox/mesh-controller/examples/route-proxy 1.136s
ok github.com/novox/mesh-controller/internal/artifacts 1.066s
ok github.com/novox/mesh-controller/internal/broker 2.608s
ok github.com/novox/mesh-controller/internal/builder 1.826s
ok github.com/novox/mesh-controller/internal/catalogue 4.390s
ok github.com/novox/mesh-controller/internal/conditions 2.430s
ok github.com/novox/mesh-controller/internal/envfile 1.038s
ok github.com/novox/mesh-controller/internal/facts 1.038s
ok github.com/novox/mesh-controller/internal/identity 4.127s
ok github.com/novox/mesh-controller/internal/inventory 72.019s
ok github.com/novox/mesh-controller/internal/lease 17.670s
ok github.com/novox/mesh-controller/internal/licences 3.699s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.047s
ok github.com/novox/mesh-controller/internal/link 50.994s
ok github.com/novox/mesh-controller/internal/lint 2.014s
ok github.com/novox/mesh-controller/internal/outward 1.060s
ok github.com/novox/mesh-controller/internal/overlay 1.051s
ok github.com/novox/mesh-controller/internal/secrets 1.409s
ok github.com/novox/mesh-controller/internal/store 3.280s
ok github.com/novox/mesh-controller/internal/testbus 1.205s
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.
hq issue 364 (hq #269). The gate runs
module checkover the touched manifests only, soclaude-code(mesh-catalog #170) addinguses: [operator-channel]is refused: the router's declaration is not in the set. The command's documentation already says such a seat is a note.MESH_MODULE_CHECK_SOME=1.uses/claim of a seat none of the given manifests declares is printed as a note and not counted; without it (the catalogue's merge-check over every manifest, registration) it stays a refusal.Test:
TestASeatAnotherModuleDeclaresIsANoteOverSomeManifests. Fullgo vet ./...andgo test ./...pass locally.mesh-catalog #170's gate stays red until this is merged and delivered.
Delivery
novox/mesh-controller@7b5c063cd377— delivered since 2026-10-10T10:21:40ZDelivery 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
7b5c063cmesh/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 ace as
build-1791597249170720305(builds --log build-1791597249170720305).