L3 final: the node-engine reads core-credentials and tool-runner with no fallback, and states its manifest reads (ADR 0601 §4, ADR 0614 §4, issue 774) #203

Merged

mesh-tools merged 24 commits from feat/l3-final into main 2026-11-04 00:23:57 +00:00

Conversation 2 Commits 24 Files Changed 48

+1181 -161

mesh-tools commented 2026-11-03 22:50:53 +00:00

Member

Copy Link

Copy Source

One delivery group, branch feat/l3-final in mesh-sdk, mesh-delivery, mesh-catalog, mesh-tools and mesh-host: the final release of design 47's step L3 (issue 774, with 1367 and 1585).

This member:

• The reviewed L3 node-engine commits a24a1d7..a0ce37f (the words read with no fallback; a module whose manifest lacks them keeps what runs, ADR 0601 §4).
• The node record states manifest-reads from the mesh-sdk built in (ADR 0614 §4). Its own manifest needs nothing beyond the baseline, so the running node-engines are not held from receiving it.
• After check 278aa5f0ccbe failed: compose.Input carries the held mark over the bus, and the sandbox names a module the input's engine holds ("its node-engine holds it: ") instead of failing on its stub as "0 bundle(s)".
• Pins mesh-sdk 85ba0a9a70d8.
  What the operator sees: the node-engine updates itself on all four nodes.
  Tests: unit count unchanged; one integration test added (under 50).

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

https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

One delivery group, branch feat/l3-final in mesh-sdk, mesh-delivery, mesh-catalog, mesh-tools and mesh-host: the final release of design 47's step L3 (issue 774, with 1367 and 1585). This member: - The reviewed L3 node-engine commits a24a1d7..a0ce37f (the words read with no fallback; a module whose manifest lacks them keeps what runs, ADR 0601 §4). - The node record states `manifest-reads` from the mesh-sdk built in (ADR 0614 §4). Its own manifest needs nothing beyond the baseline, so the running node-engines are not held from receiving it. - After check 278aa5f0ccbe failed: compose.Input carries the held mark over the bus, and the sandbox names a module the input's engine holds ("its node-engine holds it: <why>") instead of failing on its stub as "0 bundle(s)". - Pins mesh-sdk 85ba0a9a70d8. What the operator sees: the node-engine updates itself on all four nodes. Tests: unit count unchanged; one integration test added (under 50). Reviewed-by: mesh-code-reviewer@shanks at 30b86ea602a8f157bcd05aad745c44f32ef7897c Pushed-by: lead-47@shanks https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools added 23 commits 2026-11-03 22:50:53 +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) a24a1d72ad

Pin mesh-sdk b7abe203a929, the group's head of feat/l3b-bus: it keeps, deprecated, the exported names the running parts still use ... a0ce37fb2c

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

Pin mesh-sdk 85ba0a9a70d8, the head of feat/l3-final: the contract states the reader capabilities a node-engine reads and the node record carries them (ADR 0614 §4, issue 774) ... 3544d644ba

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

The node record states the reader capabilities of the mesh-sdk the engine is built with (ADR 0614 §4, issue 774) ... 32a99144f6

recordOf writes catalogue.ManifestReads in NodeRecord.ManifestReads, once per build, so the assigner moves a want only
to an engine that reads its manifest. A row holds the engine's own manifest to the baseline's words, so its new build is
never held for a word only it reads.

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools commented 2026-11-03 22:50:58 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-host@30b86ea602a8 — merged since 2026-11-04T00:24:02Z

Source — source.main moved to novox/mesh-host@83e135f101. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group feat/l3-final: novox/mesh-catalog@6c09be4a70, novox/mesh-delivery@70ade15c36, novox/mesh-host@30b86ea602, novox/mesh-sdk@85ba0a9a70, novox/mesh-tools@7fd9d893c0

• composed together: pass — the checker's verdict at the members' heads (d6a3e805db4a)

Transitions

• 2026-11-03 23:56 (new) → proposed (announced): novox/mesh-host#203's head announced
• 2026-11-03 23:56 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-04 00:24 ready → merged (merged): on the trunk its modules follow: merged there

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-delivery:view --> **Delivery** `novox/mesh-host@30b86ea602a8` — **merged** since 2026-11-04T00:24:02Z **Source** — source.main moved to novox/mesh-host@83e135f10187. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/l3-final`: novox/mesh-catalog@6c09be4a703e, novox/mesh-delivery@70ade15c36eb, novox/mesh-host@30b86ea602a8, novox/mesh-sdk@85ba0a9a70d8, novox/mesh-tools@7fd9d893c0a5 - composed together: pass — the checker's verdict at the members' heads (d6a3e805db4a) **Transitions** - 2026-11-03 23:56 (new) → proposed (announced): novox/mesh-host#203's head announced - 2026-11-03 23:56 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-04 00:24 ready → merged (merged): on the trunk its modules follow: merged there 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 commented 2026-11-03 23:36:26 +00:00

Author

Member

Copy Link

Copy Source

mesh-delivery: not merged. The merge of this pull request into main at 32a99144f6 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-delivery: **not merged.** The merge of this pull request into main at 32a99144f65e27c13b7db4fdb6d78b4fecd21f50 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

jschoubben added 1 commit 2026-11-03 23:56:54 +00:00

An input carries the modules it holds as their stubs across the bus, and the sandbox names why the node-engine holds one (issue 774, group check 278aa5f0ccbe) ... 30b86ea602

The stub's mark (Manifest.Stubbed) is no field of a manifest's JSON, so an input a node-engine sent the check's
sandbox lost it: node-tools, held by its manifest's verdict, read as a tool runner with no bundle and refused every
module of ace, g14 and shanks for "its build produced 0 bundle(s)". compose.Input now writes its held modules (catalogue
and each node's kept) beside its fields and marks them again on reading; an input from an engine before the mark is
read by its contract, every module Refused names held as its stub. The sandbox composer also says, in the module's
read, why the input's node-engine holds a module the case carries, so the check names the cause, not a rule about the
stub. One subtest round-trips an input holding a refused tool runner, in both shapes; it refused for 0 bundles before.

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

mesh-tools merged commit 83e135f101 into main 2026-11-04 00:23:57 +00:00

mesh-tools deleted branch feat/l3-final 2026-11-04 00:23:57 +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

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#203