Delivery group feat/r4g-finish (design 47, milestone R4g+R5, its finish): hq, mesh-sdk, mesh-controller, mesh-delivery, mesh-catalog, mesh-media-catalog, mesh-host. One Approve, one delivery plan.
This member: mesh-build-go runs the compose job on node-build-go's check stream (go/cmd/mesh-compose; 1621, 1622, 1623); the digest never keeps a package marked reads-outside and folds the module's non-Go files in (1935), with 41 markers; merge-check.sh gone (1295); mesh-build-go pinned to the group's mesh-sdk head bfc3883a. Main merged in (#471). The group's check judges it.
Reviewed-by: review-r4g-r3@shanks at 2fabbe556e
Pushed-by: lead-47@shanks
Delivery group feat/r4g-finish (design 47, milestone R4g+R5, its finish): hq, mesh-sdk, mesh-controller, mesh-delivery, mesh-catalog, mesh-media-catalog, mesh-host. One Approve, one delivery plan.
This member: mesh-build-go runs the compose job on node-build-go's check stream (go/cmd/mesh-compose; 1621, 1622, 1623); the digest never keeps a package marked reads-outside and folds the module's non-Go files in (1935), with 41 markers; merge-check.sh gone (1295); mesh-build-go pinned to the group's mesh-sdk head bfc3883a. Main merged in (#471). The group's check judges it.
Reviewed-by: review-r4g-r3@shanks at 2fabbe556e73e0625e755435815f52192823afbc
Pushed-by: lead-47@shanks
mesh/check failed: shanks: novox/mesh-catalog#473: modules/mesh-build-go/go.mod names mesh-sdk bc0c25e51052, which is neither on mesh-sdk's trunk nor …
forticlient waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
minio waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
minio provides s3-bucket: its consumers are sent again after it
minio keeps data (ADR 0233): what it holds is backed up before it moves
networkmanager waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
postgres provides postgres-database: its consumers are sent again after it
postgres keeps data (ADR 0233): what it holds is backed up before it moves
systemd-networkd waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
xorg provides x11-display: its consumers are sent again after it
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 adwaita, blueman, brother, i3, lemurs, mesh-build-go, mesh-build-image, mesh-build-node, mesh-mail-notifier, mesh-provisioner-client, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, slack, xorg, xterm is judged on its first machine
composed together: pass — the checker's verdict at the members' heads (590ced519c20)
Machines
adwaita on every machine running it: sent
blueman on every machine running it: sent
brother on every machine running it: sent
forticlient on every machine running it: sent
i3 on every machine running it: sent
lemurs on every machine running it: sent
mesh-build-image on every machine running it: sent
mesh-build-node on every machine running it: sent
mesh-delivery-builder on every machine running it: sent
mesh-delivery-checker on every machine running it: sent
mesh-delivery-gate on every machine running it: sent
mesh-delivery-indexer on every machine running it: sent
mesh-delivery-teller on every machine running it: sent
mesh-delivery-watchman on every machine running it: sent
mesh-host on every machine running it: sent
mesh-issues on every machine running it: sent
mesh-knowledge on every machine running it: sent
mesh-mail on every machine running it: sent
mesh-mail-notifier on every machine running it: sent
mesh-mail-reader on every machine running it: sent
mesh-provisioner-client on every machine running it: sent
mesh-sdk on every machine running it: sent
minio on every machine running it: sent
networkmanager on every machine running it: sent
nextcloud-client on every machine running it: sent
nm-applet on every machine running it: sent
openrazer on every machine running it: sent
pacman on every machine running it: sent
polychromatic on every machine running it: sent
postgres on every machine running it: sent
slack on every machine running it: sent
systemd-networkd on every machine running it: sent
xorg on every machine running it: sent
xterm on every machine running it: sent
mesh-controller on every machine running it: sent
mesh-build-go on every machine running it: sent
mesh-delivery-assigner on every machine running it: sent
Transitions
2026-10-24 12:57 (new) → proposed (announced): novox/mesh-catalog#473's head announced
2026-10-24 13:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-24 13:12 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-24 14:20 rejected → proposed (recheck): its mesh/check judged it again: pass 2fabbe556e on 25176e1ccd | judged by the candidate's mesh-build-go at 1c0eb1a8c88c
2026-10-24 14:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-24 14:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-24 19:47 ready → proposed (trunk moved): out of date: judged against trunk 25176e1ccd, the trunk is now ee216e4e63f1; judged again on a recheck or when it is merged
2026-10-24 20:56 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
2026-10-24 20:59 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
2026-10-24 21:11 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@2fabbe556e73` — **delivered** since 2026-10-24T21:11:25Z
**Delivery plan** — builds adwaita, blueman, brother, forticlient, i3, lemurs, mesh-build-go, mesh-build-image, mesh-build-node, mesh-delivery-gate, mesh-issues, mesh-knowledge, mesh-mail, mesh-mail-notifier, mesh-mail-reader, mesh-provisioner-client, minio, networkmanager, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, postgres, slack, systemd-networkd, xorg, xterm → ace, g14, novox, shanks; no bus step; 9 wait(s) for a person
- tier 0: adwaita, blueman, brother, forticlient, i3, lemurs, mesh-build-go, mesh-build-image, mesh-build-node, mesh-delivery-gate, mesh-issues, mesh-knowledge, mesh-mail, mesh-mail-notifier, mesh-mail-reader, mesh-provisioner-client, minio, networkmanager, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, postgres, slack, systemd-networkd, xorg, xterm
- ace: receives mesh-provisioner-client, pacman; waits for a person: networkmanager, postgres
- g14: receives adwaita, blueman, i3, lemurs, mesh-build-go, mesh-build-node, mesh-mail-notifier, mesh-provisioner-client, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, slack, xorg, xterm; waits for a person: forticlient, networkmanager
- novox: receives mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-issues, mesh-knowledge, mesh-mail, mesh-mail-reader, mesh-provisioner-client, pacman; waits for a person: minio, postgres, systemd-networkd
- shanks: receives adwaita, blueman, brother, i3, lemurs, mesh-build-go, mesh-build-image, mesh-build-node, mesh-mail-notifier, mesh-provisioner-client, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, slack, xorg, xterm; waits for a person: forticlient, networkmanager
- forticlient waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
- minio waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
- minio provides s3-bucket: its consumers are sent again after it
- minio keeps data (ADR 0233): what it holds is backed up before it moves
- networkmanager waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
- postgres waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
- postgres provides postgres-database: its consumers are sent again after it
- postgres keeps data (ADR 0233): what it holds is backed up before it moves
- systemd-networkd waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
- xorg provides x11-display: its consumers are sent again after it
- 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 adwaita, blueman, brother, i3, lemurs, mesh-build-go, mesh-build-image, mesh-build-node, mesh-mail-notifier, mesh-provisioner-client, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, slack, xorg, xterm is judged on its first machine
**Group** `feat/r4g-finish`: novox/hq@2249d30151e8, novox/mesh-catalog@2fabbe556e73, novox/mesh-controller@ecbb317dc324, novox/mesh-delivery@65496fc4f7a6, novox/mesh-host@13bdcb694be0, novox/mesh-media-catalog@6392690b90c2, novox/mesh-sdk@bfc3883af980
- composed together: pass — the checker's verdict at the members' heads (590ced519c20)
**Machines**
- adwaita on every machine running it: sent
- blueman on every machine running it: sent
- brother on every machine running it: sent
- forticlient on every machine running it: sent
- i3 on every machine running it: sent
- lemurs on every machine running it: sent
- mesh-build-image on every machine running it: sent
- mesh-build-node on every machine running it: sent
- mesh-delivery-builder on every machine running it: sent
- mesh-delivery-checker on every machine running it: sent
- mesh-delivery-gate on every machine running it: sent
- mesh-delivery-indexer on every machine running it: sent
- mesh-delivery-teller on every machine running it: sent
- mesh-delivery-watchman on every machine running it: sent
- mesh-host on every machine running it: sent
- mesh-issues on every machine running it: sent
- mesh-knowledge on every machine running it: sent
- mesh-mail on every machine running it: sent
- mesh-mail-notifier on every machine running it: sent
- mesh-mail-reader on every machine running it: sent
- mesh-provisioner-client on every machine running it: sent
- mesh-sdk on every machine running it: sent
- minio on every machine running it: sent
- networkmanager on every machine running it: sent
- nextcloud-client on every machine running it: sent
- nm-applet on every machine running it: sent
- openrazer on every machine running it: sent
- pacman on every machine running it: sent
- polychromatic on every machine running it: sent
- postgres on every machine running it: sent
- slack on every machine running it: sent
- systemd-networkd on every machine running it: sent
- xorg on every machine running it: sent
- xterm on every machine running it: sent
- mesh-controller on every machine running it: sent
- mesh-build-go on every machine running it: sent
- mesh-delivery-assigner on every machine running it: sent
**Transitions**
- 2026-10-24 12:57 (new) → proposed (announced): novox/mesh-catalog#473's head announced
- 2026-10-24 13:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-24 13:12 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
- 2026-10-24 14:20 rejected → proposed (recheck): its mesh/check judged it again: pass 2fabbe556e73 on 25176e1ccdb3 | judged by the candidate's mesh-build-go at 1c0eb1a8c88c
- 2026-10-24 14:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-24 14:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-24 19:47 ready → proposed (trunk moved): out of date: judged against trunk 25176e1ccdb3, the trunk is now ee216e4e63f1; judged again on a recheck or when it is merged
- 2026-10-24 20:56 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
- 2026-10-24 20:59 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go`
- 2026-10-24 21:11 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/check failed: shanks: novox/mesh-catalog#473: modules/mesh-build-go/go.mod names mesh-sdk 19c1d35939bc, which is neither on mesh-sdk's trunk nor …
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
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.
Delivery group feat/r4g-finish (design 47, milestone R4g+R5, its finish): hq, mesh-sdk, mesh-controller, mesh-delivery, mesh-catalog, mesh-media-catalog, mesh-host. One Approve, one delivery plan.
This member: mesh-build-go runs the compose job on node-build-go's check stream (go/cmd/mesh-compose; 1621, 1622, 1623); the digest never keeps a package marked reads-outside and folds the module's non-Go files in (1935), with 41 markers; merge-check.sh gone (1295); mesh-build-go pinned to the group's mesh-sdk head bfc3883a. Main merged in (#471). The group's check judges it.
Reviewed-by: review-r4g-r3@shanks at
2fabbe556ePushed-by: lead-47@shanks
Delivery
novox/mesh-catalog@2fabbe556e73— delivered since 2026-10-24T21:11:25ZDelivery plan — builds adwaita, blueman, brother, forticlient, i3, lemurs, mesh-build-go, mesh-build-image, mesh-build-node, mesh-delivery-gate, mesh-issues, mesh-knowledge, mesh-mail, mesh-mail-notifier, mesh-mail-reader, mesh-provisioner-client, minio, networkmanager, nextcloud-client, nm-applet, openrazer, pacman, polychromatic, postgres, slack, systemd-networkd, xorg, xterm → ace, g14, novox, shanks; no bus step; 9 wait(s) for a person
Group
feat/r4g-finish: novox/hq@2249d30151, novox/mesh-catalog@2fabbe556e, novox/mesh-controller@ecbb317dc3, novox/mesh-delivery@65496fc4f7, novox/mesh-host@13bdcb694b, novox/mesh-media-catalog@6392690b90, novox/mesh-sdk@bfc3883af9Machines
Transitions
2fabbe556eon25176e1ccd| judged by the candidate's mesh-build-go at 1c0eb1a8c88c25176e1ccd, the trunk is now ee216e4e63f1; judged again on a recheck or when it is mergedplans goThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.