The have bucket and its grants, a module and build per resource, the bus's connect events for the watchman, and a new module registered at its merge's Approve (issues 1136, 1145, 1147, 1146) #383

Merged

mesh-tools merged 12 commits from feat/delivery-have into main 2026-10-18 18:36:13 +00:00

Conversation 1 Commits 12 Files Changed 36

+1940 -86

mesh-tools commented 2026-10-18 17:34:23 +00:00

Member

Copy Link

Copy Source

Design 47, release 1-2, cut B: one delivery group with mesh-host's feat/delivery-have.

• Issue 1136 (ADR 0429 §1): the controller asserts node-engine_have (history 20) and grants each node read and write of its own keys <node>.> only, the controller none; a module's reads of node-engine.have is read-only. The SDK is re-pinned at mesh-sdk 2b420603fe83 (the old pin, mesh-sdk #28's head, is on no branch: issue 1148).
• Issue 1145: each resource's module and each module's builds are sent only to a node whose report says reads_modules (migration 0106); any other node gets today's body byte for byte. mesh-host is pinned at 9d9e3a46c4f5.
• Issue 1147 (ADR 0431, accepted): the composed accounts file declares $SYS with no user, exporting MESH's connect and disconnect events and its connections request; MESH imports them as mesh.bus.connect, mesh.bus.disconnect, mesh.bus.connz, granted to mesh-delivery-watchman alone. The integration test reloads the pinned server with it and needs no restart.
• Issue 1146 (ADR 0432, approved by its review, waiting for the operator's Approve): the first module of a repository no registered module is built from is registered when its build is of a merge announced as made on the operator's Approve of that head; the forge's checks are unchanged; a later module of that repository is judged as before.

Tests: 1136/AC1-AC4, 1145/AC1-AC4, 1146/AC1-AC5, 1147/AC1-AC3. Try build-1792344581798464299 passed in 3 m 38 s (unit level 2295 tests, 2.62 s of 5 s).
Code lines (acceptance test 20; non-test Go, no blank or comment lines): 111,612 on this branch, 111,432 on main (+180); research 063's baseline 111,386.
Delivery: the controller to novox, with the node-engine of this group to every machine.

Reviewed-by: reviewer-r12@shanks at 06bf8cb2fb

Design 47, release 1-2, cut B: one delivery group with mesh-host's feat/delivery-have. - Issue 1136 (ADR 0429 §1): the controller asserts `node-engine_have` (history 20) and grants each node read and write of its own keys `<node>.>` only, the controller none; a module's `reads` of `node-engine.have` is read-only. The SDK is re-pinned at mesh-sdk 2b420603fe83 (the old pin, mesh-sdk #28's head, is on no branch: issue 1148). - Issue 1145: each resource's `module` and each module's `builds` are sent only to a node whose report says `reads_modules` (migration 0106); any other node gets today's body byte for byte. mesh-host is pinned at 9d9e3a46c4f5. - Issue 1147 (ADR 0431, accepted): the composed accounts file declares `$SYS` with no user, exporting MESH's connect and disconnect events and its connections request; MESH imports them as `mesh.bus.connect`, `mesh.bus.disconnect`, `mesh.bus.connz`, granted to `mesh-delivery-watchman` alone. The integration test reloads the pinned server with it and needs no restart. - Issue 1146 (ADR 0432, approved by its review, waiting for the operator's Approve): the first module of a repository no registered module is built from is registered when its build is of a merge announced as made on the operator's Approve of that head; the forge's checks are unchanged; a later module of that repository is judged as before. Tests: 1136/AC1-AC4, 1145/AC1-AC4, 1146/AC1-AC5, 1147/AC1-AC3. Try build-1792344581798464299 passed in 3 m 38 s (unit level 2295 tests, 2.62 s of 5 s). Code lines (acceptance test 20; non-test Go, no blank or comment lines): 111,612 on this branch, 111,432 on main (+180); research 063's baseline 111,386. Delivery: the controller to novox, with the node-engine of this group to every machine. Reviewed-by: reviewer-r12@shanks at 06bf8cb2fb7a6b34c7999629848b61c35c059bfd

mesh-tools added 12 commits 2026-10-18 17:34:23 +00:00

Pin the SDK with delivery's keys, from a commit the forge keeps (issue 1136) ... 6746ab6492

The old pin named mesh-sdk #28's head, which no branch holds, so a fresh
download of the controller could not fetch it.

A new module from a repository nothing registered is built from registers on the operator's Approve of its merge (issue 1146, ADR 0432) 8c0fa40e65

The broker asserts the have bucket and grants each node its own keys of it, the controller none (issue 1136) 661e8eff2f

A second new module from a repository is judged alongside, with no warrant asked: test (issue 1146, AC5) 557c11af1e

The bus's system account exports MESH's connect and disconnect events and connections request, heard only by the watchman (issue 1147) 8c8bc5021e

Merge branch 'feat/delivery-have-broker' into feat/delivery-have fc43238267

Send each resource's module and each module's build to a node that reads them; pin mesh-host at 0b391f49a25f (issue 1145) dc65fe2319

Test that declarationWith sets modules and builds for a node that reads them (issue 1145); the Approve of a head it did not cover refuses a new module, heads keyed by the repository (issue 1146) 2d3d5ab616

Pin mesh-host at 9d9e3a46c4f5 and recapture it beside (issue 1145) eba864dc5f

The connections request asks for user names, which the server leaves out otherwise (issue 1147) 0520773412

Judge migration 105 alone now that 106 follows it, and list the new store tests (issue 1145) 222c9c1d72

Merge branch 'feat/delivery-have-broker' into feat/delivery-have 06bf8cb2fb

mesh-tools commented 2026-10-18 17:34:32 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-controller@06bf8cb2fb7a — delivering since 2026-10-18T18:37:53Z

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-have: novox/mesh-controller@06bf8cb2fb, novox/mesh-host@aab65b81f6

• composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Transitions

• 2026-10-18 17:34 (new) → proposed (announced): novox/mesh-controller#383's head announced
• 2026-10-18 17:39 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-18 17:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-18 18:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-18 18:37 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

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-controller@06bf8cb2fb7a` — **delivering** since 2026-10-18T18:37:53Z **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-have`: novox/mesh-controller@06bf8cb2fb7a, novox/mesh-host@aab65b81f65c - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Transitions** - 2026-10-18 17:34 (new) → proposed (announced): novox/mesh-controller#383's head announced - 2026-10-18 17:39 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 17:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 18:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 18:37 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 The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 461fa9c7b4 into main 2026-10-18 18:36:13 +00:00

mesh-tools deleted branch feat/delivery-have 2026-10-18 18:36:13 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#383