L3: a new node is set up without the old catalog module, and the seat table takes mesh-catalog from the SDK (ADR 0604) #202

2026-11-03T16:59:44Z

mesh-tools commented

2026-11-03 16:59:44 +00:00

Milestone L3 of design 47, one delivery group on branch feat/l3b-bus with mesh-sdk, mesh-delivery, mesh-catalog and mesh-tools; pins mesh-sdk cf5812101b0b. The node-engine's code.

Genesis installs no catalog module (ADR 0604).
The seat table takes the SDK's mesh-catalog entry with its four verbs (ADR 0604 §1).
Carried from L3a: the review rounds' fixes.

Issue: 774.

Reviewed-by: mesh-code-reviewer@shanks at a24a1d72ad
Pushed-by: lead-47@shanks

https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

Milestone L3 of design 47, one delivery group on branch feat/l3b-bus with mesh-sdk, mesh-delivery, mesh-catalog and mesh-tools; pins mesh-sdk cf5812101b0b. The node-engine's code. - Genesis installs no catalog module (ADR 0604). - The seat table takes the SDK's mesh-catalog entry with its four verbs (ADR 0604 §1). - Carried from L3a: the review rounds' fixes. Issue: 774. Reviewed-by: mesh-code-reviewer@shanks at a24a1d72ad45a7a2484f109aa988edc4d72d8a56 Pushed-by: lead-47@shanks https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools added 20 commits 2026-11-03 16:59:45 +00:00

The sandbox composes a node as its node-engine does, from an input that says how, and names a node it cannot judge from an older engine's input (issue 774, ADR 0593 §9) 7b8f5e7805

The sandbox fails a node whose change refuses a module the node-engine did not hold, in that module's words, instead of passing it with the rest composed (issue 774, review of the sandbox input) 03b7fcd7bb

The node agent's applies run through a runner its options name, so one integration test proves the bus module's first want takes the bus server over from the node's own composition without moving it, and a build that changes it replaces it once (ADR 0599 §4, §6) 23cbf9294a

The sandbox refuses no module the node holds composing without the change, a module blamed for a refusal among them (issue 774, review round 1) 649ed21d55

The node-engine carries a module's own secrets sealed by the vault when its manifest says they are the core's credentials, pinned at mesh-sdk 4f141ff (issue 774, the operator 2026-11-03) 12c80d7c2e

The node-engine finds the tool runner by what its manifest says (tool-runner), never by its name, pinned at mesh-sdk a973bfa (issue 774, the operator 2026-11-03) db7cd273f0

The sandbox's composer marks a node it does not judge in the contract's field (Machine.NotJudged), neither composed nor refused, never by a prefix of its reason (ADR 0593 §9; the prepare's seams finding on "not judged") 6ea23b6731

A node agent that meets a manifest which does not yet say it is the tool runner, or that its own secrets are the core's credentials, keeps what runs of it, its tool runner process and its sealed secrets alike, known by what runs and said; never composed without it (ADR 0601 §4) faa2005538

A have waiting for a yes says whether the move changes the build alone: the composer composes the build the module runs with today's settings and secrets and the agent compares it with what runs, so a release's Approve answers it and a changed setting is still asked (ADR 0601 §1) 5b455cecfe

The integration test of the bus module's first want shows its node backing it up through the backup seat before that apply and before the one that replaces the server, as every module that keeps data (ADR 0601 §2) 75e3a26336

Pin mesh-sdk 09ec82cb3551, the group's head of feat/l3b-bus (ADR 0601) b461b005e9

What a node keeps of a module as it runs, for a manifest that does not yet say it, is carried on the module's have by module, so the watchman raises its condition (ADR 0601 §4; review round 1, finding 3) 7da4deb3f1

Rows for the composer's composition of today: the same inputs give the running digest, a changed input another, a build it cannot compose none (ADR 0601 §1; review round 1, finding 2) 2239fb253d

The witness judges the tool runner's process by its id, <its module>.runtime, which the composition gives only the module whose manifest says it is the tool runner, never by a name (ADR 0601 §4; review round 1, finding 4) b47668421f

The bus module's integration test publishes the backup's end at once: the node agent hears it before it asks, so no sleep (review round 1, finding 5) 72bcf20870

Pin mesh-sdk 825483043549, the group's head of feat/l3b-bus (review round 1) 98719a1bd5

Pin mesh-sdk e7ce86ff62b5, the group's head of feat/l3b-bus (review round 2) c777fbae8f

Genesis installs no catalog module: the catalogue step and the take of mesh-catalog go (ADR 0604 section 7, issue 774) 53b0e8d318

Pin mesh-sdk 65b7adc8bdd9; the seat table here takes the SDK's mesh-catalog entry with its four verbs (ADR 0604 section 1) 02c7f8e052

Pin mesh-sdk cf5812101b0b, the group's final head: the module graph is no part of mesh-sdk (ADR 0603, ADR 0604, issue 1367)

mesh/delivery-group group feat/l3b-bus rejected: composed together: the checker's verdict at the members' heads (a1cb9beeb97a): unit: modules/mesh-provisioner.…

Details

mesh/delivery closed: the pull request closed unmerged

Details

mesh/check failed (4): unit: modules/mesh-provisioner.gofmt: not as gofmt writes them (run gofmt -w): modul…; and 3 more | a24a1d72ad45 on 798d73eb11e9

a24a1d72ad

mesh-tools commented

2026-11-03 16:59:49 +00:00

Delivery novox/mesh-host@a24a1d72ad45 — closed since 2026-11-03T17:51:31Z

Group feat/l3b-bus: novox/mesh-catalog@1a35e5cf4d, novox/mesh-delivery@51deed51e3, novox/mesh-sdk@cf5812101b, novox/mesh-tools@db3dd04be7

Transitions

2026-11-03 16:59 (new) → proposed (announced): novox/mesh-host#202's head announced
2026-11-03 16:59 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-03 17:51 ready → closed (closed): the pull request closed unmerged

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-host@a24a1d72ad45` — **closed** since 2026-11-03T17:51:31Z **Group** `feat/l3b-bus`: novox/mesh-catalog@1a35e5cf4dc6, novox/mesh-delivery@51deed51e3b4, novox/mesh-sdk@cf5812101b0b, novox/mesh-tools@db3dd04be7b6 **Transitions** - 2026-11-03 16:59 (new) → proposed (announced): novox/mesh-host#202's head announced - 2026-11-03 16:59 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-03 17:51 ready → closed (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools closed this pull request

2026-11-03 17:51:30 +00:00

mesh-tools commented

2026-11-03 17:51:34 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head a24a1d72ad is no longer the pull request's head, or the pull request closed. 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: its head a24a1d72ad45 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#202