Design 47 milestone R3b (ADR 0437 §3, §5, §6, §9, §11), one delivery group with mesh-catalog's feat/delivery-seat-by-claim (the messenger). The operator sees no change.
issue 1214: the builder computes the source fingerprint with mesh-sdk's one function (delivery.SourceFingerprint); mesh-sdk pinned at main aa68b673; every fingerprint byte-identical.
issue 1215: a build record carries its fingerprint's inputs (source-inputs, mesh-sdk's SourceInputs) from the builder to chain.Build.
issue 1210: the controller's own path and the merge gate's rule find the delivery's module by its claim of the seat mesh-delivery, not its name.
issue 1211: a merge's announcement is heard from whichever module claims the seat (one wildcard subject), and refused from any other.
issue 1212: the controller names the seat holders' pulls buckets on each check; the build agent reads those (falls back to mesh-delivery_pulls). The build agent's read grant for the gate's bucket is R3d's.
issue 1213: a merge's warrant is read under the asker the announcement names, accepted only for mesh-delivery-teller and mesh-delivery.
issue 1216: a test proves a module may say a condition only under its own name (the composed grant).
Tests from each issue's acceptance criteria. Review: 2 rounds (one finding, 1212's wiring test). Try build-1792404582477148045 passed (4m32s).
Design 47 milestone R3b (ADR 0437 §3, §5, §6, §9, §11), one delivery group with mesh-catalog's feat/delivery-seat-by-claim (the messenger). The operator sees no change.
- issue 1214: the builder computes the source fingerprint with mesh-sdk's one function (delivery.SourceFingerprint); mesh-sdk pinned at main aa68b673; every fingerprint byte-identical.
- issue 1215: a build record carries its fingerprint's inputs (source-inputs, mesh-sdk's SourceInputs) from the builder to chain.Build.
- issue 1210: the controller's own path and the merge gate's rule find the delivery's module by its claim of the seat mesh-delivery, not its name.
- issue 1211: a merge's announcement is heard from whichever module claims the seat (one wildcard subject), and refused from any other.
- issue 1212: the controller names the seat holders' pulls buckets on each check; the build agent reads those (falls back to mesh-delivery_pulls). The build agent's read grant for the gate's bucket is R3d's.
- issue 1213: a merge's warrant is read under the asker the announcement names, accepted only for mesh-delivery-teller and mesh-delivery.
- issue 1216: a test proves a module may say a condition only under its own name (the composed grant).
Tests from each issue's acceptance criteria. Review: 2 rounds (one finding, 1212's wiring test). Try build-1792404582477148045 passed (4m32s).
Reviewed-by: reviewer-r3b@shanks at 3e7f34d041b1e1aaa3ccface2825aae332628d2b
mesh/merge-gate head 3e7f34d041b1 merged into trunk 59c8cf2f2406 — pass: group feat/delivery-seat-by-claim composed: every machine composes with the change…
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
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 route-proxy, build-agent is judged on its first machine
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-controller on every machine running it: sent
route-proxy on every machine running it: sent
build-agent on every machine running it: sent
messenger on every machine running it: sent
Transitions
2026-10-19 10:17 (new) → proposed (announced): novox/mesh-controller#394's head announced
2026-10-19 10:24 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 10:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 10:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-19 10:30 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-19 10:39 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@3e7f34d041b1` — **delivered** since 2026-10-19T10:39:55Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller, route-proxy
- tier 1: build-agent
- ace: receives route-proxy, build-agent
- g14: receives build-agent
- novox: receives mesh-controller, route-proxy, build-agent
- shanks: receives build-agent
- 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
- 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 route-proxy, build-agent is judged on its first machine
**Group** `feat/delivery-seat-by-claim`: novox/mesh-catalog@5aca005cb741, novox/mesh-controller@3e7f34d041b1
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-controller on every machine running it: sent
- route-proxy on every machine running it: sent
- build-agent on every machine running it: sent
- messenger on every machine running it: sent
**Transitions**
- 2026-10-19 10:17 (new) → proposed (announced): novox/mesh-controller#394's head announced
- 2026-10-19 10:24 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 10:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 10:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-19 10:30 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-19 10:39 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`.
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
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 route-proxy, build-agent is judged on its first machine
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.
Design 47 milestone R3b (ADR 0437 §3, §5, §6, §9, §11), one delivery group with mesh-catalog's feat/delivery-seat-by-claim (the messenger). The operator sees no change.
Tests from each issue's acceptance criteria. Review: 2 rounds (one finding, 1212's wiring test). Try build-1792404582477148045 passed (4m32s).
Reviewed-by: reviewer-r3b@shanks at
3e7f34d041Delivery
novox/mesh-controller@3e7f34d041b1— delivered since 2026-10-19T10:39:55ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Group
feat/delivery-seat-by-claim: novox/mesh-catalog@5aca005cb7, novox/mesh-controller@3e7f34d041Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
3e7f34d0Judged: head
3e7f34d041b1merged into trunk59c8cf2f2406; read beside it: mesh-catalogb4527d9091e9, mesh-controller-main59c8cf2f2406, mesh-host2474bf28330f, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1792405066861770871(builds --log build-1792405066861770871).