novox/hq issue 544: neither build-agent.server nor route-proxy.server declared health, so each walk that moved them waited out the 60 s grace on every machine (build-agent judged after 1 m 45 s and route-proxy after 1 m 25 s on ace in plan-1791826579427234545).
build-agent.server: exec check /usr/local/bin/mesh-builder ready, every 10 s, 3 looks, 60 s grace. It passes once the agent is bound to its build work, after its node-build-agent verbs are served (companion PR on mesh-controller, same branch name). A tool check on a verb is not possible: the node-engine asks only a module's own tools and reads a health answer, and module check refuses a tool the module does not serve; the agent listens on nothing.
route-proxy.server: tcp check on its http endpoint (port 80), every 10 s, 3 looks, 60 s grace. tcp, not http: an http request would be refused as "no route" and logged every look, which the route-proxy jail reads; a bare connect on the plain-HTTP port logs nothing. Not the https port: a connect without a handshake is logged as a TLS handshake error.
health-undeclared 69 -> 67.
Order: after the mesh-controller change (declared above for the delivery group), so the image that knows ready rolls first. Either order would be safe: an older build-agent image answers mesh-builder ready with its usage and exit 0, so a weaker check, never a put-back.
Ran: merge-check.sh with MESH_GATE set to a controller built from main (words, agenthome, paths, module check: build-agent ready: server by exec every 10s, route-proxy ready: server by tcp on http every 10s, count 67 as kept).
after: novox/mesh-controller
novox/hq issue 544: neither build-agent.server nor route-proxy.server declared `health`, so each walk that moved them waited out the 60 s grace on every machine (build-agent judged after 1 m 45 s and route-proxy after 1 m 25 s on ace in plan-1791826579427234545).
- **build-agent.server**: exec check `/usr/local/bin/mesh-builder ready`, every 10 s, 3 looks, 60 s grace. It passes once the agent is bound to its build work, after its node-build-agent verbs are served (companion PR on mesh-controller, same branch name). A tool check on a verb is not possible: the node-engine asks only a module's own tools and reads a health answer, and `module check` refuses a tool the module does not serve; the agent listens on nothing.
- **route-proxy.server**: tcp check on its `http` endpoint (port 80), every 10 s, 3 looks, 60 s grace. tcp, not http: an http request would be refused as "no route" and logged every look, which the route-proxy jail reads; a bare connect on the plain-HTTP port logs nothing. Not the https port: a connect without a handshake is logged as a TLS handshake error.
- `health-undeclared` 69 -> 67.
Order: after the mesh-controller change (declared above for the delivery group), so the image that knows `ready` rolls first. Either order would be safe: an older build-agent image answers `mesh-builder ready` with its usage and exit 0, so a weaker check, never a put-back.
Ran: `merge-check.sh` with `MESH_GATE` set to a controller built from main (words, agenthome, paths, module check: build-agent `ready: server by exec every 10s`, route-proxy `ready: server by tcp on http every 10s`, count 67 as kept).
mesh/merge-gate head d09dbe33ac0f merged into trunk ac2d4dc46f4c — pass: builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step; every mach…
mesh/repo-check head d09dbe33ac0f merged into trunk ac2d4dc46f4c — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Neither server declared health, so each walk that moved them waited out the
60 s grace on every machine. The build agent is ready when 'mesh-builder ready'
says it took its build work; the route proxy when its http port accepts.
Deliverynovox/mesh-catalog@d09dbe33ac0f — delivered since 2026-10-12T21:31:06Z
Delivery plan — builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step
tier 0: build-agent
tier 1: route-proxy
ace: receives build-agent, route-proxy
g14: receives build-agent
novox: receives 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
Groupfix/544-the-build-agent-says-it-is-ready, in order:
mesh-delivery on novox: passed — carried by plan-1791834103351744736
mesh-issues on novox: passed — carried by plan-1791834103351744736
build-agent on ace: passed — carried by plan-1791835104096916825
route-proxy on ace: passed — carried by plan-1791837446596590979
route-proxy on the rest running it: sent
Transitions
2026-10-12 19:43 (new) → proposed (announced): novox/mesh-catalog#257's head announced
2026-10-12 19:46 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-12 19:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 20:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 20:15 published → held (hold): something holds it for a person: its group's composed check did not pass for the heads that merged, or it merged and no walk was opened for it
2026-10-12 21:20 held → delivering (release): The operator decided at 23:23: release. Held only because the group fix/544's order could not be read (an after: added to #257's description is not re-read, noted on issue 578); its controller member mesh-controller #277 is delivered (plan-1791835104096916825), and build-agent and route-proxy built with #257 already passed their gates on ace in plan-1791835104096916825 and plan-1791837446596590979. The review judged either order safe.
2026-10-12 21:31 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-catalog@d09dbe33ac0f` — **delivered** since 2026-10-12T21:31:06Z
**Delivery plan** — builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: build-agent
- tier 1: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives 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
**Group** `fix/544-the-build-agent-says-it-is-ready`, in order:
- novox/mesh-catalog@d09dbe33ac0f before novox/mesh-controller@50c55a773eb8: built by
- novox/mesh-controller@50c55a773eb8 before novox/mesh-catalog@d09dbe33ac0f: built by
- **refused**: novox/mesh-catalog@d09dbe33ac0f and novox/mesh-controller@50c55a773eb8: built by puts novox/mesh-catalog@d09dbe33ac0f first, built by puts novox/mesh-controller@50c55a773eb8 first, version skew puts novox/mesh-controller@50c55a773eb8 first; neither outranks the other: declare the order with a line `after: novox/mesh-catalog` in novox/mesh-controller#277's description, or `after: novox/mesh-controller` in novox/mesh-catalog#257's
**Machines**
- mesh-delivery on novox: passed — carried by plan-1791834103351744736
- mesh-issues on novox: passed — carried by plan-1791834103351744736
- build-agent on ace: passed — carried by plan-1791835104096916825
- route-proxy on ace: passed — carried by plan-1791837446596590979
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-12 19:43 (new) → proposed (announced): novox/mesh-catalog#257's head announced
- 2026-10-12 19:46 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-12 19:46 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 20:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 20:15 published → held (hold): something holds it for a person: its group's composed check did not pass for the heads that merged, or it merged and no walk was opened for it
- 2026-10-12 21:20 held → delivering (release): The operator decided at 23:23: release. Held only because the group fix/544's order could not be read (an `after:` added to #257's description is not re-read, noted on issue 578); its controller member mesh-controller #277 is delivered (plan-1791835104096916825), and build-agent and route-proxy built with #257 already passed their gates on ace in plan-1791835104096916825 and plan-1791837446596590979. The review judged either order safe.
- 2026-10-12 21:31 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`.
Merge check at d09dbe33
Judged: head d09dbe33ac0f merged into trunk ac2d4dc46f4c; read beside it: mesh-controller 4dbd4066ca54, mesh-controller-main c0c379af2b3c, mesh-host 303d4037e84e, mesh-tools 954e1a53eef9
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, route-proxy)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step
tier 0: build-agent
tier 1: route-proxy
ace: receives build-agent, route-proxy
g14: receives build-agent
novox: receives 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
read by no module's build: health-undeclared
Run by the build seat on shanks as build-1791834227436427380 (builds --log build-1791834227436427380).
--- the gate: build-agent, route-proxy
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
route-proxy: ok, keeps acme (rebuildable), ca (cache), ready: server by tcp on http every 10s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T19:43:51Z 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-12T19:43:51Z
modules the change moves:
- build-agent (changed)
- route-proxy (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, route-proxy
notes:
- health-undeclared read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.004s
words: 12 retired words and 70 daemons' lines, none in the 44870 strings of 704 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 67, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.357s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d09dbe33`
Judged: head `d09dbe33ac0f` merged into trunk `ac2d4dc46f4c`; read beside it: mesh-controller `4dbd4066ca54`, mesh-controller-main `c0c379af2b3c`, mesh-host `303d4037e84e`, mesh-tools `954e1a53eef9`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: build-agent
- tier 1: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives 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
- read by no module's build: health-undeclared
Run by the build seat on shanks as `build-1791834227436427380` (`builds --log build-1791834227436427380`).
```
--- the gate: build-agent, route-proxy
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
route-proxy: ok, keeps acme (rebuildable), ca (cache), ready: server by tcp on http every 10s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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 2 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T19:43:51Z 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-12T19:43:51Z
modules the change moves:
- build-agent (changed)
- route-proxy (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, route-proxy
notes:
- health-undeclared read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.004s
words: 12 retired words and 70 daemons' lines, none in the 44870 strings of 704 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 67, as kept
ok git.novox.be/novox/mesh-catalog/checks/deps 0.357s
--- its merge-check-typescript.sh (typescript toolchain)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
after: novox/mesh-controller
novox/hq issue 544: neither build-agent.server nor route-proxy.server declared
health, so each walk that moved them waited out the 60 s grace on every machine (build-agent judged after 1 m 45 s and route-proxy after 1 m 25 s on ace in plan-1791826579427234545)./usr/local/bin/mesh-builder ready, every 10 s, 3 looks, 60 s grace. It passes once the agent is bound to its build work, after its node-build-agent verbs are served (companion PR on mesh-controller, same branch name). A tool check on a verb is not possible: the node-engine asks only a module's own tools and reads a health answer, andmodule checkrefuses a tool the module does not serve; the agent listens on nothing.httpendpoint (port 80), every 10 s, 3 looks, 60 s grace. tcp, not http: an http request would be refused as "no route" and logged every look, which the route-proxy jail reads; a bare connect on the plain-HTTP port logs nothing. Not the https port: a connect without a handshake is logged as a TLS handshake error.health-undeclared69 -> 67.Order: after the mesh-controller change (declared above for the delivery group), so the image that knows
readyrolls first. Either order would be safe: an older build-agent image answersmesh-builder readywith its usage and exit 0, so a weaker check, never a put-back.Ran:
merge-check.shwithMESH_GATEset to a controller built from main (words, agenthome, paths, module check: build-agentready: server by exec every 10s, route-proxyready: server by tcp on http every 10s, count 67 as kept).Delivery
novox/mesh-catalog@d09dbe33ac0f— delivered since 2026-10-12T21:31:06ZDelivery plan — builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step
Group
fix/544-the-build-agent-says-it-is-ready, in order:after: novox/mesh-catalogin novox/mesh-controller#277's description, orafter: novox/mesh-controllerin novox/mesh-catalog#257'sMachines
Transitions
after:added to #257's description is not re-read, noted on issue 578); its controller member mesh-controller #277 is delivered (plan-1791835104096916825), and build-agent and route-proxy built with #257 already passed their gates on ace in plan-1791835104096916825 and plan-1791837446596590979. The review judged either order safe.The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
d09dbe33Judged: head
d09dbe33ac0fmerged into trunkac2d4dc46f4c; read beside it: mesh-controller4dbd4066ca54, mesh-controller-mainc0c379af2b3c, mesh-host303d4037e84e, mesh-tools954e1a53eef9mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, route-proxy)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds build-agent, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791834227436427380(builds --log build-1791834227436427380).