Carry plan-moved in the installer's first user list (hq ADR 0239) #44

2026-10-06T22:00:13Z

mesh-admin commented

2026-10-06 22:00:13 +00:00

Part of the mesh-delivery feature (hq ADR 0239, to-be 47; branch feat/mesh-delivery in mesh-controller, mesh-catalog, mesh-host).

The controller now says every walk it keeps as the seat event plan-moved. The genesis lock (examples/foundation-first-node-nats.lock) carries the controller's first user list, which must equal what the controller derives (mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose): one subject added, mesh.seat.mesh-controller.event.plan-moved.

Merge order: this first (after hq #156), and roll it out before the mesh-controller PR is checked: the controller's repo-check reads this repository beside it at the commit the mesh runs.

Tested: merge-check.sh (gofmt, vet, go test -race ./...) passes; the controller's genesis-template test passes against this checkout.

Part of the mesh-delivery feature (hq ADR 0239, to-be 47; branch `feat/mesh-delivery` in mesh-controller, mesh-catalog, mesh-host). The controller now says every walk it keeps as the seat event `plan-moved`. The genesis lock (`examples/foundation-first-node-nats.lock`) carries the controller's first user list, which must equal what the controller derives (mesh-controller's `TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose`): one subject added, `mesh.seat.mesh-controller.event.plan-moved`. **Merge order:** this first (after hq #156), and roll it out before the mesh-controller PR is checked: the controller's repo-check reads this repository beside it at the commit the mesh runs. Tested: `merge-check.sh` (gofmt, vet, `go test -race ./...`) passes; the controller's genesis-template test passes against this checkout.

mesh-admin added 1 commit 2026-10-06 22:00:13 +00:00

Carry plan-moved in the installer's first user list (hq ADR 0239)

mesh/merge-gate pass: every machine composes with the change as it did without (0 of 4 compose)

mesh/delivery delivered

Details

mesh/delivery-group group feat/mesh-delivery merged: every member is merged

Details

94e49c6b2d

The controller says every walk it keeps as plan-moved; a controller raised
from genesis must be allowed to say it from its first start.

mesh-admin merged commit 880e7461f9 into main

2026-10-06 22:07:19 +00:00

mesh-admin deleted branch feat/mesh-delivery

2026-10-06 22:07:20 +00:00

mesh-admin commented

2026-10-06 23:10:44 +00:00

Delivery novox/mesh-host@94e49c6b2dbd — delivered since 2026-10-06T23:05:28Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host

Group feat/mesh-delivery, in order:

Machines

mesh-host on ace: passed — healthy 3 times over 2m28s
mesh-host on the rest running it: sent

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#44's head announced
2026-10-06 23:05 proposed → checked (checked): the verdict names this commit
2026-10-06 23:05 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-06 23:05 rejected → 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-06 23:05 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-06 23:05 delivering → delivered (done): its walk is done: 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.

**Delivery** `novox/mesh-host@94e49c6b2dbd` — **delivered** since 2026-10-06T23:05:28Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Group** `feat/mesh-delivery`, in order: **Machines** - mesh-host on ace: passed — healthy 3 times over 2m28s - mesh-host on the rest running it: sent **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#44's head announced - 2026-10-06 23:05 proposed → checked (checked): the verdict names this commit - 2026-10-06 23:05 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-06 23:05 rejected → 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-06 23:05 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-06 23:05 delivering → delivered (done): its walk is done: 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-admin referenced this pull request

2026-10-06 23:39:04 +00:00

Lay out the publishing test as every gofmt agrees (hq issue 286) #46

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#44