Feature 57's release of mesh-controller, on top of main: tree a4a4e50c = the release branch (#346, #353 for issue 876) merged with main d70bb1f3 (17 files resolved, keeping issue 867's sibling checks and feature 57), plus testdata/beside captured at mesh-host bff1ac14. Two commits: the patch, and the seven golden files' blank last line the patch route drops (issue 875). Review of the merge: in progress (Opus). Route approved by the operator 10:26. Delivery group bundle A with mesh-sdk #30, mesh-host #116 and hq #378.
Right after its delivery: mesh-controller.secret-move. Until then machines on contract 12 raise an Urgent vault-silent condition (review C r1 finding 3, issue 755).
Feature 57's release of mesh-controller, on top of main: tree a4a4e50c = the release branch (#346, #353 for issue 876) merged with main d70bb1f3 (17 files resolved, keeping issue 867's sibling checks and feature 57), plus testdata/beside captured at mesh-host bff1ac14. Two commits: the patch, and the seven golden files' blank last line the patch route drops (issue 875). Review of the merge: in progress (Opus). Route approved by the operator 10:26. Delivery group bundle A with mesh-sdk #30, mesh-host #116 and hq #378.
Right after its delivery: mesh-controller.secret-move. Until then machines on contract 12 raise an Urgent vault-silent condition (review C r1 finding 3, issue 755).
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
Transitions
2026-10-16 08:29 (new) → proposed (announced): novox/mesh-controller#355's head announced
2026-10-16 08:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 08:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 08:43 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-16 08:43 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-16 08:49 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@8c381172e7ea` — **delivered** since 2026-10-16T08:49:29Z
**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** `release/57-config-and-provisioning`, in order: novox/hq@e7417cf1248c → novox/mesh-controller@8c381172e7ea → novox/mesh-host@bff1ac14a198 → novox/mesh-sdk@1bc5719b8b85
- novox/mesh-controller@8c381172e7ea before novox/mesh-host@bff1ac14a198: built by, over engine before controller
- novox/mesh-controller@8c381172e7ea before novox/mesh-sdk@1bc5719b8b85: built by
- 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
**Transitions**
- 2026-10-16 08:29 (new) → proposed (announced): novox/mesh-controller#355's head announced
- 2026-10-16 08:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-16 08:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-16 08:43 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-16 08:43 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-16 08:49 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
Tree a4a4e50c = the release branch merged with main (review APPROVE, Opus, round 1, at 1fc4e730). The operator's word for releasing feature 57: 10:10 and 10:26; notice of the delivery's Urgent vault-silent notices sent 10:39.
ready at 8c381172e7ea51e8461c52eaf41c52c18573cf97
Tree a4a4e50c = the release branch merged with main (review APPROVE, Opus, round 1, at 1fc4e730). The operator's word for releasing feature 57: 10:10 and 10:26; notice of the delivery's Urgent vault-silent notices sent 10:39.
mesh-delivery: the ready mark at is cleared: the head is now 8c381172e7, pushed after it. Mark the new head ready once it is reviewed.
mesh-delivery: the ready mark at is cleared: the head is now 8c381172e7ea51e8461c52eaf41c52c18573cf97, pushed after it. Mark the new head ready once it is reviewed.
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.
Feature 57's release of mesh-controller, on top of main: tree
a4a4e50c= the release branch (#346, #353 for issue 876) merged with maind70bb1f3(17 files resolved, keeping issue 867's sibling checks and feature 57), plus testdata/beside captured at mesh-host bff1ac14. Two commits: the patch, and the seven golden files' blank last line the patch route drops (issue 875). Review of the merge: in progress (Opus). Route approved by the operator 10:26. Delivery group bundle A with mesh-sdk #30, mesh-host #116 and hq #378.Right after its delivery: mesh-controller.secret-move. Until then machines on contract 12 raise an Urgent vault-silent condition (review C r1 finding 3, issue 755).
Delivery
novox/mesh-controller@8c381172e7ea— delivered since 2026-10-16T08:49:29ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Group
release/57-config-and-provisioning, in order: novox/hq@e7417cf124 → novox/mesh-controller@8c381172e7 → novox/mesh-host@bff1ac14a1 → novox/mesh-sdk@1bc5719b8bMachines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
8c381172Judged: head
8c381172e7eamerged into trunkd70bb1f38867; read beside it: mesh-catalog173c5d5ef434, mesh-controller-maind70bb1f38867, mesh-host328401284c93, mesh-tools6b3e15042feeSiblings read beside it: novox/mesh-host#116
bff1ac14a198merged onto49c9002c04d3(main); judged by this change's own merge8c381172e7mesh/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 novox as
build-1792139380390571980(builds --log build-1792139380390571980).ready at
8c381172e7Tree
a4a4e50c= the release branch merged with main (review APPROVE, Opus, round 1, at 1fc4e730). The operator's word for releasing feature 57: 10:10 and 10:26; notice of the delivery's Urgent vault-silent notices sent 10:39.mesh-delivery: the ready mark at is cleared: the head is now
8c381172e7, pushed after it. Mark the new head ready once it is reviewed.ready at
8c381172e7Marked again (issue 873: the label was cleared).