Declares the own-secret genesis-package-registry at ${dir:mesh-state}/genesis-package-registry.json, issued-by: outside: only the installer gives one, on genesis's node; no other machine gets a file (§3).
The agent's environment names MESH_GENESIS_PACKAGE_REGISTRY=/run/mesh/genesis-package-registry.json, read by mesh-controller's cmd/mesh-builder while no binding is present.
Binds and secrets for the registry: the manifest has no per-entry only-when-bound form for binds/secrets (they are maps of paths); ADR 0330 §6 composes neither for an absent requirement, and no file names them through a placeholder, which the test holds.
README says the above.
Why
Genesis stopped at step 13: mesh-controller assign anchor build-agent -> "nothing provides "npm-package-registry", wanted by build-agent" (issue 121's note of 2026-10-13).
Tested
New modules/build-agent/manifest_test.go (with a dependency-free go.mod so merge-check runs it): fails on main (optional requirement, genesis own-secret), passes here.
MESH_GATE=<controller from this change's mesh-controller branch> MESH_CHECK_MODULES=build-agent sh merge-check.sh: passes; module check build-agent: ok.
Goes with mesh-controller (cmd/mesh-builder, internal/builder) and mesh-host (packages step) pull requests for the same issue. Merge this one first: the controller's catalogue tests read the catalogue's main.
Fixes issue 121 (with the mesh-controller and mesh-host pull requests).
## What
- `build-agent` requires `npm-package-registry` with `optional: true` (ADR 0336 §1, ADR 0330 §1); `artifact-store` stays hard.
- Declares the own-secret `genesis-package-registry` at `${dir:mesh-state}/genesis-package-registry.json`, `issued-by: outside`: only the installer gives one, on genesis's node; no other machine gets a file (§3).
- The agent's environment names `MESH_GENESIS_PACKAGE_REGISTRY=/run/mesh/genesis-package-registry.json`, read by mesh-controller's cmd/mesh-builder while no binding is present.
- Binds and secrets for the registry: the manifest has no per-entry `only-when-bound` form for `binds`/`secrets` (they are maps of paths); ADR 0330 §6 composes neither for an absent requirement, and no file names them through a placeholder, which the test holds.
- README says the above.
## Why
Genesis stopped at step 13: `mesh-controller assign anchor build-agent` -> "nothing provides \"npm-package-registry\", wanted by build-agent" (issue 121's note of 2026-10-13).
## Tested
- New `modules/build-agent/manifest_test.go` (with a dependency-free go.mod so merge-check runs it): fails on main (optional requirement, genesis own-secret), passes here.
- `MESH_GATE=<controller from this change's mesh-controller branch> MESH_CHECK_MODULES=build-agent sh merge-check.sh`: passes; module check `build-agent: ok`.
Goes with mesh-controller (cmd/mesh-builder, internal/builder) and mesh-host (packages step) pull requests for the same issue. Merge this one first: the controller's catalogue tests read the catalogue's main.
Fixes issue 121 (with the mesh-controller and mesh-host pull requests).
mesh/merge-gate head e0bc919d4945 merged into trunk f88e3452f8b8 — pass: builds build-agent → ace, g14, novox, shanks; no bus step; every machine composes …
mesh/repo-check head e0bc919d4945 merged into trunk f88e3452f8b8 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/delivery covered: a later merge that contains it was delivered: novox/mesh-catalog@2f5e97030a5c (merged as 5cd608ba into main, walk plan-17918799551…
build-agent's npm-package-registry becomes optional, so genesis's step 13 is no
longer refused with 'nothing provides npm-package-registry'. Until gitea is
assigned, the agent on genesis's node reads the genesis-package-registry
own-secret the installer seals at the packages step; it is issued outside the
mesh, so no other machine is given one. The binding and its credential are
composed only while bound (ADR 0330 §6), and no file names them otherwise.
Deliverynovox/mesh-catalog@e0bc919d4945 — covered since 2026-10-13T08:40:26Z
Delivery plan — builds build-agent → ace, g14, novox, shanks; no bus step
tier 0: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives 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
build-agent on ace: passed — carried by plan-1791862719602485401
route-proxy on ace: passed — carried by plan-1791867557600646669
Transitions
2026-10-13 00:56 (new) → proposed (announced): novox/mesh-catalog#263's head announced
2026-10-13 00:58 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 00:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 03:33 ready → proposed (recheck): re-judge the 121 delivery group after #289 named its order (after: novox/mesh-catalog)
2026-10-13 03:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 03:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 03:46 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-13 03:46 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-13 08:40 held → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-catalog@2f5e97030a (merged as 5cd608ba into main, walk plan-1791879955106134684): build-agent
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@e0bc919d4945` — **covered** since 2026-10-13T08:40:26Z
**Delivery plan** — builds build-agent → ace, g14, novox, shanks; no bus step
- tier 0: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives 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
**Group** `fix/121-genesis-package-registry`, in order: novox/hq@39830983ccf1 → novox/mesh-host@5f147fe6b9c7
- novox/mesh-catalog@e0bc919d4945 before novox/mesh-controller@a641ed7d15c7: built by
- novox/mesh-controller@a641ed7d15c7 before novox/mesh-catalog@e0bc919d4945: built by
- **refused**: novox/mesh-catalog@e0bc919d4945 and novox/mesh-controller@a641ed7d15c7: built by puts novox/mesh-catalog@e0bc919d4945 first, built by puts novox/mesh-controller@a641ed7d15c7 first, version skew puts novox/mesh-controller@a641ed7d15c7 first; neither outranks the other: declare the order with a line `after: novox/mesh-catalog` in novox/mesh-controller#289's description, or `after: novox/mesh-controller` in novox/mesh-catalog#263's
**Machines**
- build-agent on ace: passed — carried by plan-1791862719602485401
- route-proxy on ace: passed — carried by plan-1791867557600646669
**Transitions**
- 2026-10-13 00:56 (new) → proposed (announced): novox/mesh-catalog#263's head announced
- 2026-10-13 00:58 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 00:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 03:33 ready → proposed (recheck): re-judge the 121 delivery group after #289 named its order (after: novox/mesh-catalog)
- 2026-10-13 03:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 03:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 03:46 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-13 03:46 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-13 08:40 held → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-catalog@2f5e97030a5c (merged as 5cd608ba into main, walk plan-1791879955106134684): build-agent
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Merge check at e0bc919d
Judged: head e0bc919d4945 merged into trunk f88e3452f8b8; read beside it: mesh-controller 4473bc7d7315, mesh-controller-main 49102e1645c9, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent)
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 → ace, g14, novox, shanks; no bus step
tier 0: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives 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: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go
Run by the build seat on ace as build-1791853011476602769 (builds --log build-1791853011476602769).
--- the gate: build-agent
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
long-running resources without health: 0
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-13T00:28:25Z 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-13T00:28:25Z
modules the change moves:
- build-agent (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 1 module(s) in 1 tier(s): build-agent
notes:
- modules/build-agent/README.md, modules/build-agent/go.mod and modules/build-agent/manifest_test.go 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.002s
words: 12 retired words and 70 daemons' lines, none in the 46085 strings of 712 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
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.227s
testing modules/build-agent
ok build-agent 1.010s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `e0bc919d`
Judged: head `e0bc919d4945` merged into trunk `f88e3452f8b8`; read beside it: mesh-controller `4473bc7d7315`, mesh-controller-main `49102e1645c9`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent)
- `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 → ace, g14, novox, shanks; no bus step
- tier 0: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives 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: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go
Run by the build seat on ace as `build-1791853011476602769` (`builds --log build-1791853011476602769`).
```
--- the gate: build-agent
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
long-running resources without health: 0
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-13T00:28:25Z 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-13T00:28:25Z
modules the change moves:
- build-agent (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 1 module(s) in 1 tier(s): build-agent
notes:
- modules/build-agent/README.md, modules/build-agent/go.mod and modules/build-agent/manifest_test.go 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.002s
words: 12 retired words and 70 daemons' lines, none in the 46085 strings of 712 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
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.227s
testing modules/build-agent
ok build-agent 1.010s
--- its merge-check-typescript.sh (typescript toolchain)
```
Independent review against ADR 0336 (read whole, with reasoning) and ADR 0330.
No blocking finding in the change. The merge has one precondition outside the code: the delivery group fix/121-genesis-package-registry reads rejected (see the statuses below). mesh-controller #289 now carries the line after: novox/mesh-catalog, which resolves the contradiction in the order this PR goes first, but the group was judged before that line and needs a recheck. Merge only after mesh/delivery-group is green.
What I checked:
The manifest does what ADR 0336 §1 and §3 ask. npm-package-registry is {name, optional: true}, artifact-store stays a bare (hard) name, and the own-secret genesis-package-registry is declared issued-by: outside at ${dir:mesh-state}/genesis-package-registry.json, which the environment file names as /run/mesh/genesis-package-registry.json. On controller main, an own-secret issued outside and not given composes no file (declaration.go, issue 401), so the build agent on a machine other than genesis's gets nothing and no needs-operator wait.
Tests fail without the change. I ran modules/build-agent's tests against main's module.json: TestThePackageRegistryIsOptionalAndTheArtifactStoreStaysHard and TestTheGenesisDocumentIsDeclaredAndIssuedOutside fail; at the head all three pass. TestTheRegistrysBindsAndSecretsAreOnlyWhenBound also passes on main. It is a guard that keeps the ADR 0330 §6 premise true, not a test of this change.
MESH_GATE=<controller main 584ee991> MESH_CHECK_MODULES=build-agent sh merge-check.sh passes locally (67 long-running resources without health, as kept).
The builder's choice (a), judged against the ADR. ADR 0336 §1 says the requirement's binds and secrets entries are "declared only-when-bound", and its How it is checked says a catalogue test asserts it. No manifest form allows that: binds and secrets are maps of name to path, and the controller's OptionalProblems refuses only-when-bound on anything but a file resource (ADR 0330 §5). The effect the clause wants already holds by ADR 0330 §6, which composes no binding, secret or grant for an absent requirement, and the controller test in #289 shows no bound file and no secret file in the declaration while the registry is unbound. I accept the choice. It is not blocking, but the accepted record now states something the mesh does not do: ADR 0336 §1 and its How it is checked need a progressive insight through knowledge-base.propose (with insight) saying binds and secrets are not composed by ADR 0330 §6, because no only-when-bound form exists for them.
Non-blocking: the README paragraph's first line was joined onto a long line ("the artifact store as a provision, a workspace, and the bus credential. The code is ...") and is now much wider than the rest of the file.
Statuses at this head:
mesh/merge-gate: success, "head e0bc919d49 merged into trunk f88e3452f8 — pass: builds build-agent → ace, g14, novox, shanks; no bus step; every machine composes …"
mesh/repo-check: success, "head e0bc919d49 merged into trunk f88e3452f8 — pass: its merge-check.sh passed, each part in its toolchain"
mesh/delivery: success, "ready: it delivers once merged"
mesh/delivery-group: failure, "group fix/121-genesis-package-registry rejected: its order contradicts itself: novox/mesh-catalog@e0bc919d49 and novox/mesh-controller@a6…"
Verdict: approve at e0bc919d4945bb5f13f971f74643a0b714cf45da
Independent review against ADR 0336 (read whole, with reasoning) and ADR 0330.
No blocking finding in the change. The merge has one precondition outside the code: the delivery group fix/121-genesis-package-registry reads rejected (see the statuses below). mesh-controller #289 now carries the line `after: novox/mesh-catalog`, which resolves the contradiction in the order this PR goes first, but the group was judged before that line and needs a recheck. Merge only after mesh/delivery-group is green.
What I checked:
1. The manifest does what ADR 0336 §1 and §3 ask. `npm-package-registry` is `{name, optional: true}`, `artifact-store` stays a bare (hard) name, and the own-secret `genesis-package-registry` is declared `issued-by: outside` at `${dir:mesh-state}/genesis-package-registry.json`, which the environment file names as /run/mesh/genesis-package-registry.json. On controller main, an own-secret issued outside and not given composes no file (declaration.go, issue 401), so the build agent on a machine other than genesis's gets nothing and no needs-operator wait.
2. Tests fail without the change. I ran modules/build-agent's tests against main's module.json: TestThePackageRegistryIsOptionalAndTheArtifactStoreStaysHard and TestTheGenesisDocumentIsDeclaredAndIssuedOutside fail; at the head all three pass. TestTheRegistrysBindsAndSecretsAreOnlyWhenBound also passes on main. It is a guard that keeps the ADR 0330 §6 premise true, not a test of this change.
3. `MESH_GATE=<controller main 584ee991> MESH_CHECK_MODULES=build-agent sh merge-check.sh` passes locally (67 long-running resources without health, as kept).
The builder's choice (a), judged against the ADR. ADR 0336 §1 says the requirement's `binds` and `secrets` entries are "declared only-when-bound", and its How it is checked says a catalogue test asserts it. No manifest form allows that: `binds` and `secrets` are maps of name to path, and the controller's OptionalProblems refuses `only-when-bound` on anything but a file resource (ADR 0330 §5). The effect the clause wants already holds by ADR 0330 §6, which composes no binding, secret or grant for an absent requirement, and the controller test in #289 shows no bound file and no secret file in the declaration while the registry is unbound. I accept the choice. It is not blocking, but the accepted record now states something the mesh does not do: ADR 0336 §1 and its How it is checked need a progressive insight through knowledge-base.propose (with `insight`) saying binds and secrets are not composed by ADR 0330 §6, because no only-when-bound form exists for them.
Non-blocking: the README paragraph's first line was joined onto a long line ("the artifact store as a provision, a workspace, and the bus credential. The code is ...") and is now much wider than the rest of the file.
Statuses at this head:
- mesh/merge-gate: success, "head e0bc919d4945 merged into trunk f88e3452f8b8 — pass: builds build-agent → ace, g14, novox, shanks; no bus step; every machine composes …"
- mesh/repo-check: success, "head e0bc919d4945 merged into trunk f88e3452f8b8 — pass: its merge-check.sh passed, each part in its toolchain"
- mesh/delivery: success, "ready: it delivers once merged"
- mesh/delivery-group: failure, "group fix/121-genesis-package-registry rejected: its order contradicts itself: novox/mesh-catalog@e0bc919d4945 and novox/mesh-controller@a6…"
Merge check at e0bc919d
Judged: head e0bc919d4945 merged into trunk f88e3452f8b8; read beside it: mesh-controller 4473bc7d7315, mesh-controller-main 584ee991961c, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent)
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 → ace, g14, novox, shanks; no bus step
tier 0: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives 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: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go
Run by the build seat on g14 as build-1791862418331605511 (builds --log build-1791862418331605511).
--- the gate: build-agent
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
long-running resources without health: 0
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-13T00:28:25Z 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-13T00:28:25Z
modules the change moves:
- build-agent (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 1 module(s) in 1 tier(s): build-agent
notes:
- modules/build-agent/README.md, modules/build-agent/go.mod and modules/build-agent/manifest_test.go 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.002s
words: 12 retired words and 70 daemons' lines, none in the 46085 strings of 712 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s
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.409s
testing modules/build-agent
ok build-agent 1.007s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `e0bc919d`
Judged: head `e0bc919d4945` merged into trunk `f88e3452f8b8`; read beside it: mesh-controller `4473bc7d7315`, mesh-controller-main `584ee991961c`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent)
- `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 → ace, g14, novox, shanks; no bus step
- tier 0: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives 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: modules/build-agent/README.md, modules/build-agent/go.mod, modules/build-agent/manifest_test.go
Run by the build seat on g14 as `build-1791862418331605511` (`builds --log build-1791862418331605511`).
```
--- the gate: build-agent
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
long-running resources without health: 0
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-13T00:28:25Z 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-13T00:28:25Z
modules the change moves:
- build-agent (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 1 module(s) in 1 tier(s): build-agent
notes:
- modules/build-agent/README.md, modules/build-agent/go.mod and modules/build-agent/manifest_test.go 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.002s
words: 12 retired words and 70 daemons' lines, none in the 46085 strings of 712 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s
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.409s
testing modules/build-agent
ok build-agent 1.007s
--- 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.
What
build-agentrequiresnpm-package-registrywithoptional: true(ADR 0336 §1, ADR 0330 §1);artifact-storestays hard.genesis-package-registryat${dir:mesh-state}/genesis-package-registry.json,issued-by: outside: only the installer gives one, on genesis's node; no other machine gets a file (§3).MESH_GENESIS_PACKAGE_REGISTRY=/run/mesh/genesis-package-registry.json, read by mesh-controller's cmd/mesh-builder while no binding is present.only-when-boundform forbinds/secrets(they are maps of paths); ADR 0330 §6 composes neither for an absent requirement, and no file names them through a placeholder, which the test holds.Why
Genesis stopped at step 13:
mesh-controller assign anchor build-agent-> "nothing provides "npm-package-registry", wanted by build-agent" (issue 121's note of 2026-10-13).Tested
modules/build-agent/manifest_test.go(with a dependency-free go.mod so merge-check runs it): fails on main (optional requirement, genesis own-secret), passes here.MESH_GATE=<controller from this change's mesh-controller branch> MESH_CHECK_MODULES=build-agent sh merge-check.sh: passes; module checkbuild-agent: ok.Goes with mesh-controller (cmd/mesh-builder, internal/builder) and mesh-host (packages step) pull requests for the same issue. Merge this one first: the controller's catalogue tests read the catalogue's main.
Fixes issue 121 (with the mesh-controller and mesh-host pull requests).
Delivery
novox/mesh-catalog@e0bc919d4945— covered since 2026-10-13T08:40:26ZDelivery plan — builds build-agent → ace, g14, novox, shanks; no bus step
Group
fix/121-genesis-package-registry, in order: novox/hq@39830983cc → novox/mesh-host@5f147fe6b9after: novox/mesh-catalogin novox/mesh-controller#289's description, orafter: novox/mesh-controllerin novox/mesh-catalog#263'sMachines
Transitions
5cd608bainto main, walk plan-1791879955106134684): build-agentThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
e0bc919dJudged: head
e0bc919d4945merged into trunkf88e3452f8b8; read beside it: mesh-controller4473bc7d7315, mesh-controller-main49102e1645c9, mesh-host7a41e120635b, mesh-tools954e1a53eef9mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent)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 → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791853011476602769(builds --log build-1791853011476602769).Verdict: approve at
e0bc919d49Independent review against ADR 0336 (read whole, with reasoning) and ADR 0330.
No blocking finding in the change. The merge has one precondition outside the code: the delivery group fix/121-genesis-package-registry reads rejected (see the statuses below). mesh-controller #289 now carries the line
after: novox/mesh-catalog, which resolves the contradiction in the order this PR goes first, but the group was judged before that line and needs a recheck. Merge only after mesh/delivery-group is green.What I checked:
npm-package-registryis{name, optional: true},artifact-storestays a bare (hard) name, and the own-secretgenesis-package-registryis declaredissued-by: outsideat${dir:mesh-state}/genesis-package-registry.json, which the environment file names as /run/mesh/genesis-package-registry.json. On controller main, an own-secret issued outside and not given composes no file (declaration.go, issue 401), so the build agent on a machine other than genesis's gets nothing and no needs-operator wait.MESH_GATE=<controller main 584ee991> MESH_CHECK_MODULES=build-agent sh merge-check.shpasses locally (67 long-running resources without health, as kept).The builder's choice (a), judged against the ADR. ADR 0336 §1 says the requirement's
bindsandsecretsentries are "declared only-when-bound", and its How it is checked says a catalogue test asserts it. No manifest form allows that:bindsandsecretsare maps of name to path, and the controller's OptionalProblems refusesonly-when-boundon anything but a file resource (ADR 0330 §5). The effect the clause wants already holds by ADR 0330 §6, which composes no binding, secret or grant for an absent requirement, and the controller test in #289 shows no bound file and no secret file in the declaration while the registry is unbound. I accept the choice. It is not blocking, but the accepted record now states something the mesh does not do: ADR 0336 §1 and its How it is checked need a progressive insight through knowledge-base.propose (withinsight) saying binds and secrets are not composed by ADR 0330 §6, because no only-when-bound form exists for them.Non-blocking: the README paragraph's first line was joined onto a long line ("the artifact store as a provision, a workspace, and the bus credential. The code is ...") and is now much wider than the rest of the file.
Statuses at this head:
e0bc919d49merged into trunkf88e3452f8— pass: builds build-agent → ace, g14, novox, shanks; no bus step; every machine composes …"e0bc919d49merged into trunkf88e3452f8— pass: its merge-check.sh passed, each part in its toolchain"Merge check at
e0bc919dJudged: head
e0bc919d4945merged into trunkf88e3452f8b8; read beside it: mesh-controller4473bc7d7315, mesh-controller-main584ee991961c, mesh-host7a41e120635b, mesh-tools954e1a53eef9mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent)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 → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791862418331605511(builds --log build-1791862418331605511).