Why (issue 525). ADR 0304 §4 lowers a leaf delivery's budget to three minutes. mesh-delivery's times keeps its own copy of the budgets; grouped with mesh-controller's branch of the same name so the controller's over-budget probe and times say the same budget.
What changes (modules/mesh-delivery): budgets leaf 3 min, the verb's description, and the tests: exactly 3m within, 3m01s over; the class test's figures moved under the new budget (1m, 2m within; 6m over; line "2 of 3 within 3m0s"); a 4m40s delivery is now over.
Checked: merge-check.sh with the controller from main: mesh-delivery ok; go test -race green.
**Why** (issue 525). ADR 0304 §4 lowers a leaf delivery's budget to three minutes. mesh-delivery's `times` keeps its own copy of the budgets; grouped with mesh-controller's branch of the same name so the controller's over-budget probe and `times` say the same budget.
**What changes** (modules/mesh-delivery): `budgets` leaf 3 min, the verb's description, and the tests: exactly 3m within, 3m01s over; the class test's figures moved under the new budget (1m, 2m within; 6m over; line "2 of 3 within 3m0s"); a 4m40s delivery is now over.
**Checked**: `merge-check.sh` with the controller from main: mesh-delivery ok; `go test -race` green.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-controller on novox: passed — healthy 3 times over 3m51s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 1 times over 1m41s
build-agent on the rest running it: sent
mesh-delivery on novox: passed — healthy 3 times over 2m12s
mesh-delivery on the rest running it: sent
Transitions
2026-10-11 23:45 (new) → proposed (announced): novox/mesh-catalog#227's head announced
2026-10-11 23:48 proposed → checked (checked): the verdict names this commit
2026-10-11 23:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 00:04 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 00:04 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:17 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@2711e812c89d` — **delivered** since 2026-10-12T00:17:21Z
**Delivery plan** — builds mesh-delivery → novox; no bus step
- tier 0: mesh-delivery
- novox: receives mesh-delivery
**Group** `feat/525-leaf-budget-three-minutes`, in order: novox/mesh-controller@e6bd8f1deec4 → novox/mesh-catalog@2711e812c89d
- novox/mesh-controller@e6bd8f1deec4 before novox/mesh-catalog@2711e812c89d: built by
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m51s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 1 times over 1m41s
- build-agent on the rest running it: sent
- mesh-delivery on novox: passed — healthy 3 times over 2m12s
- mesh-delivery on the rest running it: sent
**Transitions**
- 2026-10-11 23:45 (new) → proposed (announced): novox/mesh-catalog#227's head announced
- 2026-10-11 23:48 proposed → checked (checked): the verdict names this commit
- 2026-10-11 23:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 00:04 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 00:04 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:17 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: mesh-delivery)
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 mesh-delivery → novox; no bus step
tier 0: mesh-delivery
novox: receives mesh-delivery
read by no module's build: modules/mesh-delivery/cmd/mesh-delivery/times_test.go
Run by the build seat on g14 as build-1791762352535373529 (builds --log build-1791762352535373529).
--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
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 0 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
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): mesh-delivery
notes:
- modules/mesh-delivery/cmd/mesh-delivery/times_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.003s
words: 12 retired words and 70 daemons' lines, none in the 42158 strings of 680 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.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-delivery
ok mesh-delivery/cmd/mesh-delivery 2.678s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `2711e812`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery)
- `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 mesh-delivery → novox; no bus step
- tier 0: mesh-delivery
- novox: receives mesh-delivery
- read by no module's build: modules/mesh-delivery/cmd/mesh-delivery/times_test.go
Run by the build seat on g14 as `build-1791762352535373529` (`builds --log build-1791762352535373529`).
```
--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
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 0 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
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): mesh-delivery
notes:
- modules/mesh-delivery/cmd/mesh-delivery/times_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.003s
words: 12 retired words and 70 daemons' lines, none in the 42158 strings of 680 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.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-delivery
ok mesh-delivery/cmd/mesh-delivery 2.678s
--- 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.
Why (issue 525). ADR 0304 §4 lowers a leaf delivery's budget to three minutes. mesh-delivery's
timeskeeps its own copy of the budgets; grouped with mesh-controller's branch of the same name so the controller's over-budget probe andtimessay the same budget.What changes (modules/mesh-delivery):
budgetsleaf 3 min, the verb's description, and the tests: exactly 3m within, 3m01s over; the class test's figures moved under the new budget (1m, 2m within; 6m over; line "2 of 3 within 3m0s"); a 4m40s delivery is now over.Checked:
merge-check.shwith the controller from main: mesh-delivery ok;go test -racegreen.Delivery
novox/mesh-catalog@2711e812c89d— delivered since 2026-10-12T00:17:21ZDelivery plan — builds mesh-delivery → novox; no bus step
Group
feat/525-leaf-budget-three-minutes, in order: novox/mesh-controller@e6bd8f1dee → novox/mesh-catalog@2711e812c8Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
2711e812mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery)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 mesh-delivery → novox; no bus step
Run by the build seat on g14 as
build-1791762352535373529(builds --log build-1791762352535373529).