Why (issue 524, ADR 0304 §3 and §6). ADR 0282 §4 decided the first-node gate's readings by class and ADR 0304 §3 (accepted 2026-10-12, the operator's Approve) takes a leaf module to one reading. The gate never learned either: gatePasses = 3 for every build, with the two-minute settle, so mesh-media-catalog #25 (two leaf containers) spent 2m34s judging on ace and mesh-catalog #226 (netcheck, tools only) three passes too. ADR 0304 §6 has this built before the rest of 0304 (issue 525).
What changes (cmd/mesh-controller/gate.go)
coreModule: on the controller's own path (onTheControllersPath), a core component, or claiming the resolver seat — ADR 0282 §1's definition, the one classOf uses for budgets.
gateWants: a core module needs three passes after gateSettle; a leaf module one, no settle. A send needs what its most demanding module needs (a send carrying the node tools is judged as the core); each module's own pass (passedAlone) uses its own class.
PlanGate.Wants (JSON in the plan's modules, no migration): the passes the send needs, said in the status line ("1 of 1 passes"); a gate judged before reads as three.
Everything else of ADR 0236's gate stands: a reading only once the node-engine states the module healthy, no witness rollback, no condition since the send, the ten-minute bound, the rollback.
Tests (make check, a Postgres raised: every package ok, cmd/mesh-controller 647 s)
New: TestALeafModulePassesOnOneHealthyReading (passes on its first healthy judging with gateSettle an hour); TestAModuleIsJudgedByItsClass (app, nzbget: 1; mesh-controller, mesh-host, node-tools, nats, a resolver holder: 3 with settle).
13 existing tests judge the gate's other rules (rollback, the bound, supersession, tiers, the release backlog) with a leaf module app that had to stay judging after a healthy reading; each now calls judgeLeavesAsTheCore(t) so it keeps testing what it was written for. None of them showed a fault in the class rule: each failed only because a leaf now passes on its first reading (e.g. TestATierPutsABrokenModuleBackAtOnce: app1 gets its own pass at the same judging the node tools break, so the send decides at once, as the rule says).
Core: this is the controller. One rollout at a time; nothing else of the controller or node-engine is mid-gate.
**Why** (issue 524, ADR 0304 §3 and §6). ADR 0282 §4 decided the first-node gate's readings by class and ADR 0304 §3 (accepted 2026-10-12, the operator's Approve) takes a leaf module to one reading. The gate never learned either: `gatePasses = 3` for every build, with the two-minute settle, so mesh-media-catalog #25 (two leaf containers) spent 2m34s judging on ace and mesh-catalog #226 (netcheck, tools only) three passes too. ADR 0304 §6 has this built before the rest of 0304 (issue 525).
**What changes** (`cmd/mesh-controller/gate.go`)
- `coreModule`: on the controller's own path (`onTheControllersPath`), a core component, or claiming the resolver seat — ADR 0282 §1's definition, the one `classOf` uses for budgets.
- `gateWants`: a core module needs three passes after `gateSettle`; a leaf module one, no settle. A send needs what its most demanding module needs (a send carrying the node tools is judged as the core); each module's own pass (`passedAlone`) uses its own class.
- `PlanGate.Wants` (JSON in the plan's `modules`, no migration): the passes the send needs, said in the status line ("1 of 1 passes"); a gate judged before reads as three.
- Everything else of ADR 0236's gate stands: a reading only once the node-engine states the module healthy, no witness rollback, no condition since the send, the ten-minute bound, the rollback.
**Tests** (`make check`, a Postgres raised: every package ok, cmd/mesh-controller 647 s)
- New: `TestALeafModulePassesOnOneHealthyReading` (passes on its first healthy judging with `gateSettle` an hour); `TestAModuleIsJudgedByItsClass` (app, nzbget: 1; mesh-controller, mesh-host, node-tools, nats, a resolver holder: 3 with settle).
- 13 existing tests judge the gate's other rules (rollback, the bound, supersession, tiers, the release backlog) with a leaf module `app` that had to stay judging after a healthy reading; each now calls `judgeLeavesAsTheCore(t)` so it keeps testing what it was written for. None of them showed a fault in the class rule: each failed only because a leaf now passes on its first reading (e.g. `TestATierPutsABrokenModuleBackAtOnce`: app1 gets its own pass at the same judging the node tools break, so the send decides at once, as the rule says).
**Core**: this is the controller. One rollout at a time; nothing else of the controller or node-engine is mid-gate.
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
ADR 0282 decided readings by class and ADR 0304 took a leaf module to
one, but the gate never learned it: every build, leaf or core, needed
three readings over at least two minutes, so a container module that
was healthy at once still waited about two and a half minutes on its
first machine. The number of readings and the settle time now follow
the module's class: three after two minutes for the controller's own
path and the resolver, one for every other module. Tests that judge a
gate's other rules keep leaf modules on three readings.
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
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
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 1 times over 1m28s
build-agent on the rest running it: sent
Transitions
2026-10-11 23:38 (new) → proposed (announced): novox/mesh-controller#240's head announced
2026-10-11 23:51 proposed → checked (checked): the verdict names this commit
2026-10-11 23:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 23:53 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 23:53 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-12 00:01 delivering → delivered (done): its walk is done, carrying its own commit: 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@d8ec8baa2292` — **delivered** since 2026-10-12T00:01:26Z
**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
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
**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 1 times over 1m28s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-11 23:38 (new) → proposed (announced): novox/mesh-controller#240's head announced
- 2026-10-11 23:51 proposed → checked (checked): the verdict names this commit
- 2026-10-11 23:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 23:53 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 23:53 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-12 00:01 delivering → delivered (done): its walk is done, carrying its own commit: 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: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
read by no module's build: cmd/mesh-controller/gate_followup_test.go, cmd/mesh-controller/gate_test.go, cmd/mesh-controller/issue352_test.go, cmd/mesh-controller/release_test.go, cmd/mesh-controller/replay335_test.go, cmd/mesh-controller/same_source_test.go, cmd/mesh-controller/tier_send_test.go
Run by the build seat on ace as build-1791760131545214581 (builds --log build-1791760131545214581).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window 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); 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: 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-11T22:42:09Z 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-11T22:42:09Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/gate_followup_test.go, cmd/mesh-controller/gate_test.go, cmd/mesh-controller/issue352_test.go, cmd/mesh-controller/release_test.go, cmd/mesh-controller/replay335_test.go, cmd/mesh-controller/same_source_test.go and cmd/mesh-controller/tier_send_test.go read by no module's build, and rebuild nothing (issue 280)
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.058s
ok github.com/novox/mesh-controller/cmd/mesh-controller 248.089s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.057s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.047s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.043s
ok github.com/novox/mesh-controller/examples/route-proxy 1.152s
ok github.com/novox/mesh-controller/internal/artifacts 1.092s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.146s
ok github.com/novox/mesh-controller/internal/builder 16.834s
ok github.com/novox/mesh-controller/internal/catalogue 8.224s
ok github.com/novox/mesh-controller/internal/conditions 2.733s
ok github.com/novox/mesh-controller/internal/envfile 1.052s
ok github.com/novox/mesh-controller/internal/facts 1.049s
ok github.com/novox/mesh-controller/internal/identity 5.099s
ok github.com/novox/mesh-controller/internal/inventory 96.659s
ok github.com/novox/mesh-controller/internal/lease 17.757s
ok github.com/novox/mesh-controller/internal/licences 4.593s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.044s
ok github.com/novox/mesh-controller/internal/link 61.251s
ok github.com/novox/mesh-controller/internal/lint 2.423s
ok github.com/novox/mesh-controller/internal/outward 1.094s
ok github.com/novox/mesh-controller/internal/overlay 1.072s
ok github.com/novox/mesh-controller/internal/secrets 1.514s
ok github.com/novox/mesh-controller/internal/store 3.717s
ok github.com/novox/mesh-controller/internal/testbus 1.262s
ok github.com/novox/mesh-controller/internal/token 1.023s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.45s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.48s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.43s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.40s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.47s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.23s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
**Merge check** at `ad3b4f18`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
- read by no module's build: cmd/mesh-controller/gate_followup_test.go, cmd/mesh-controller/gate_test.go, cmd/mesh-controller/issue352_test.go, cmd/mesh-controller/release_test.go, cmd/mesh-controller/replay335_test.go, cmd/mesh-controller/same_source_test.go, cmd/mesh-controller/tier_send_test.go
Run by the build seat on ace as `build-1791760131545214581` (`builds --log build-1791760131545214581`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window 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); 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: 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-11T22:42:09Z 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-11T22:42:09Z
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/gate_followup_test.go, cmd/mesh-controller/gate_test.go, cmd/mesh-controller/issue352_test.go, cmd/mesh-controller/release_test.go, cmd/mesh-controller/replay335_test.go, cmd/mesh-controller/same_source_test.go and cmd/mesh-controller/tier_send_test.go read by no module's build, and rebuild nothing (issue 280)
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.058s
ok github.com/novox/mesh-controller/cmd/mesh-controller 248.089s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.057s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.047s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.043s
ok github.com/novox/mesh-controller/examples/route-proxy 1.152s
ok github.com/novox/mesh-controller/internal/artifacts 1.092s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.146s
ok github.com/novox/mesh-controller/internal/builder 16.834s
ok github.com/novox/mesh-controller/internal/catalogue 8.224s
ok github.com/novox/mesh-controller/internal/conditions 2.733s
ok github.com/novox/mesh-controller/internal/envfile 1.052s
ok github.com/novox/mesh-controller/internal/facts 1.049s
ok github.com/novox/mesh-controller/internal/identity 5.099s
ok github.com/novox/mesh-controller/internal/inventory 96.659s
ok github.com/novox/mesh-controller/internal/lease 17.757s
ok github.com/novox/mesh-controller/internal/licences 4.593s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.044s
ok github.com/novox/mesh-controller/internal/link 61.251s
ok github.com/novox/mesh-controller/internal/lint 2.423s
ok github.com/novox/mesh-controller/internal/outward 1.094s
ok github.com/novox/mesh-controller/internal/overlay 1.072s
ok github.com/novox/mesh-controller/internal/secrets 1.514s
ok github.com/novox/mesh-controller/internal/store 3.717s
ok github.com/novox/mesh-controller/internal/testbus 1.262s
ok github.com/novox/mesh-controller/internal/token 1.023s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.45s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.48s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.43s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.40s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.47s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.23s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
```
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/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
The review found that a send whose first machine runs none of its
modules would pass at once with no reading, and that every mixed send
in the tests judged its leaf as the core.
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 — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
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
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
Run by the build seat on novox as build-1791761894312002137 (builds --log build-1791761894312002137).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window 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); 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: 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-11T23:42:03Z 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-11T23:42:03Z
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
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.051s
ok github.com/novox/mesh-controller/cmd/mesh-controller 304.122s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.060s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/route-proxy 1.151s
ok github.com/novox/mesh-controller/internal/artifacts 1.063s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.309s
ok github.com/novox/mesh-controller/internal/builder 24.169s
ok github.com/novox/mesh-controller/internal/catalogue 8.873s
ok github.com/novox/mesh-controller/internal/conditions 2.913s
ok github.com/novox/mesh-controller/internal/envfile 1.030s
ok github.com/novox/mesh-controller/internal/facts 1.039s
ok github.com/novox/mesh-controller/internal/identity 6.113s
ok github.com/novox/mesh-controller/internal/inventory 128.068s
ok github.com/novox/mesh-controller/internal/lease 17.595s
ok github.com/novox/mesh-controller/internal/licences 5.602s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.012s
ok github.com/novox/mesh-controller/internal/link 65.552s
ok github.com/novox/mesh-controller/internal/lint 2.356s
ok github.com/novox/mesh-controller/internal/outward 1.036s
ok github.com/novox/mesh-controller/internal/overlay 1.022s
ok github.com/novox/mesh-controller/internal/secrets 1.514s
ok github.com/novox/mesh-controller/internal/store 3.595s
ok github.com/novox/mesh-controller/internal/testbus 1.212s
ok github.com/novox/mesh-controller/internal/token 1.016s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.90s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.78s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.53s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.68s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.48s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.43s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.56s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.37s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.39s)
**Merge check** at `d8ec8baa`
- `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** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; 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
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
Run by the build seat on novox as `build-1791761894312002137` (`builds --log build-1791761894312002137`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window 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); 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: 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-11T23:42:03Z 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-11T23:42:03Z
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
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.051s
ok github.com/novox/mesh-controller/cmd/mesh-controller 304.122s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.060s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/route-proxy 1.151s
ok github.com/novox/mesh-controller/internal/artifacts 1.063s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.309s
ok github.com/novox/mesh-controller/internal/builder 24.169s
ok github.com/novox/mesh-controller/internal/catalogue 8.873s
ok github.com/novox/mesh-controller/internal/conditions 2.913s
ok github.com/novox/mesh-controller/internal/envfile 1.030s
ok github.com/novox/mesh-controller/internal/facts 1.039s
ok github.com/novox/mesh-controller/internal/identity 6.113s
ok github.com/novox/mesh-controller/internal/inventory 128.068s
ok github.com/novox/mesh-controller/internal/lease 17.595s
ok github.com/novox/mesh-controller/internal/licences 5.602s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.012s
ok github.com/novox/mesh-controller/internal/link 65.552s
ok github.com/novox/mesh-controller/internal/lint 2.356s
ok github.com/novox/mesh-controller/internal/outward 1.036s
ok github.com/novox/mesh-controller/internal/overlay 1.022s
ok github.com/novox/mesh-controller/internal/secrets 1.514s
ok github.com/novox/mesh-controller/internal/store 3.595s
ok github.com/novox/mesh-controller/internal/testbus 1.212s
ok github.com/novox/mesh-controller/internal/token 1.016s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.90s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.78s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.53s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.68s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.48s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.43s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.56s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.37s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.39s)
```
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.
Why (issue 524, ADR 0304 §3 and §6). ADR 0282 §4 decided the first-node gate's readings by class and ADR 0304 §3 (accepted 2026-10-12, the operator's Approve) takes a leaf module to one reading. The gate never learned either:
gatePasses = 3for every build, with the two-minute settle, so mesh-media-catalog #25 (two leaf containers) spent 2m34s judging on ace and mesh-catalog #226 (netcheck, tools only) three passes too. ADR 0304 §6 has this built before the rest of 0304 (issue 525).What changes (
cmd/mesh-controller/gate.go)coreModule: on the controller's own path (onTheControllersPath), a core component, or claiming the resolver seat — ADR 0282 §1's definition, the oneclassOfuses for budgets.gateWants: a core module needs three passes aftergateSettle; a leaf module one, no settle. A send needs what its most demanding module needs (a send carrying the node tools is judged as the core); each module's own pass (passedAlone) uses its own class.PlanGate.Wants(JSON in the plan'smodules, no migration): the passes the send needs, said in the status line ("1 of 1 passes"); a gate judged before reads as three.Tests (
make check, a Postgres raised: every package ok, cmd/mesh-controller 647 s)TestALeafModulePassesOnOneHealthyReading(passes on its first healthy judging withgateSettlean hour);TestAModuleIsJudgedByItsClass(app, nzbget: 1; mesh-controller, mesh-host, node-tools, nats, a resolver holder: 3 with settle).appthat had to stay judging after a healthy reading; each now callsjudgeLeavesAsTheCore(t)so it keeps testing what it was written for. None of them showed a fault in the class rule: each failed only because a leaf now passes on its first reading (e.g.TestATierPutsABrokenModuleBackAtOnce: app1 gets its own pass at the same judging the node tools break, so the send decides at once, as the rule says).Core: this is the controller. One rollout at a time; nothing else of the controller or node-engine is mid-gate.
Delivery
novox/mesh-controller@d8ec8baa2292— delivered since 2026-10-12T00:01:26ZDelivery 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
ad3b4f18mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791760131545214581(builds --log build-1791760131545214581).Merge check at
d8ec8baamesh/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 — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; 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-1791761894312002137(builds --log build-1791761894312002137).