The node composes its own modules once the catalogue places it, and writes its record (issue 1126) #149

Merged

mesh-tools merged 17 commits from feat/1126-nodes-compose into main 2026-10-26 21:11:37 +00:00

Conversation 1 Commits 17 Files Changed 16

+1889 -29

mesh-tools commented 2026-10-26 17:35:09 +00:00

Member

Copy Link

Copy Source

Milestone L2 "nodes compose" (issue 1126; ADR 0547 §2, §3; ADR 0550 §5; ADR 0555 §3). Member of the delivery group feat/1126-nodes-compose, which the milestone's one review approved; pins mesh-sdk 979644420117 (mesh-sdk #98's head) exactly.

• The node record: the node's own have key <node>.node carries the public halves of its tunnel, sealing and serving keys, the certificate for its internal name, the mesh's authority, its present capabilities, networks, outward links and its node-engine's contract, written only when it differs.
• The node composes its own (internal/selfcompose) once placement.<node> exists: from placement, the node records, the indexer's modules and manifests, its own slice of mesh-config's values, and the vault's own (its modules' secrets and pair credentials sealed to its key, asked only when a placed module declares one). It composes again on each input's event and on the vault's secret-changed, never on a timer. A node not yet placed follows its key and begins composing its own when it appears, with no restart.
• The judgement of a move (ADR 0547 §3): a record-policy module's move waits for a yes (have phase waiting-yes, with the judgement and the digest that waits).
• A refusal is loud: when the node cannot compose (a stand-in refused, an input unread), each wanted module's have says it, failed, naming why, while it keeps running what it ran; composed again, the haves are what runs.
• Stable sealed values: the composer keeps the box the node already runs when it opens, with the node's own key, to the same value as the vault's box, so a composition stays unmoved at the switch and across restarts; the vault still seals anew at each ask.
• Tests: unit (selfcompose, agent, link, authority), with no count risen; integration H8 TestNatsANodeThePlacementNamesComposesAndAppliesItsOwn.
• Bent: H8 and the assigner's two integration tests were run once locally (embedded bus, a few seconds) to find H8's failure; the group's one check runs them as the check of record.

Reviewed-by: review-1126@shanks at 1d44288514

Milestone L2 "nodes compose" (issue 1126; ADR 0547 §2, §3; ADR 0550 §5; ADR 0555 §3). Member of the delivery group feat/1126-nodes-compose, which the milestone's one review approved; pins mesh-sdk 979644420117 (mesh-sdk #98's head) exactly. - **The node record**: the node's own have key `<node>.node` carries the public halves of its tunnel, sealing and serving keys, the certificate for its internal name, the mesh's authority, its present capabilities, networks, outward links and its node-engine's contract, written only when it differs. - **The node composes its own** (internal/selfcompose) once `placement.<node>` exists: from placement, the node records, the indexer's modules and manifests, its own slice of mesh-config's values, and the vault's `own` (its modules' secrets and pair credentials sealed to its key, asked only when a placed module declares one). It composes again on each input's event and on the vault's `secret-changed`, never on a timer. A node not yet placed follows its key and begins composing its own when it appears, with no restart. - **The judgement of a move** (ADR 0547 §3): a record-policy module's move waits for a yes (have phase waiting-yes, with the judgement and the digest that waits). - **A refusal is loud**: when the node cannot compose (a stand-in refused, an input unread), each wanted module's have says it, failed, naming why, while it keeps running what it ran; composed again, the haves are what runs. - **Stable sealed values**: the composer keeps the box the node already runs when it opens, with the node's own key, to the same value as the vault's box, so a composition stays unmoved at the switch and across restarts; the vault still seals anew at each ask. - Tests: unit (selfcompose, agent, link, authority), with no count risen; integration H8 `TestNatsANodeThePlacementNamesComposesAndAppliesItsOwn`. - Bent: H8 and the assigner's two integration tests were run once locally (embedded bus, a few seconds) to find H8's failure; the group's one check runs them as the check of record. Reviewed-by: review-1126@shanks at 1d442885148af6bf101c0404782a7b0658249c32

mesh-tools added 2 commits 2026-10-26 17:35:09 +00:00

The node agent writes what the machine observes of itself as its record in its own have key, only when it changed (issue 1126, ADR 0555 §3) 8be1c2ab0d

Pin mesh-sdk feat/1126-nodes-compose 9789c83 (issue 1126) 7fc0ea5478

mesh-tools commented 2026-10-26 17:35:15 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-host@1d442885148a — merged since 2026-10-26T21:11:39Z

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

Group feat/1126-nodes-compose: novox/hq@28d84f31bf, novox/mesh-catalog@c085975146, novox/mesh-controller@df8ebf6a77, novox/mesh-delivery@297992a4ae, novox/mesh-host@1d44288514, novox/mesh-sdk@9796444201

Transitions

• 2026-10-26 21:09 (new) → proposed (announced): novox/mesh-host#149's head announced
• 2026-10-26 21:10 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-10-26 21:11 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@1d442885148a` — **merged** since 2026-10-26T21:11:39Z **Source** — source.main moved to novox/mesh-host@be94d2689e2f. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/1126-nodes-compose`: novox/hq@28d84f31bfcb, novox/mesh-catalog@c0859751461a, novox/mesh-controller@df8ebf6a77c1, novox/mesh-delivery@297992a4ae55, novox/mesh-host@1d442885148a, novox/mesh-sdk@979644420117 **Transitions** - 2026-10-26 21:09 (new) → proposed (announced): novox/mesh-host#149's head announced - 2026-10-26 21:10 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-10-26 21:11 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`.

jschoubben added 1 commit 2026-10-26 17:45:25 +00:00

The node composes its own modules once the catalogue places it: one composer per node drains a mark set by any input's change, the agent applies what it composed when it differs, and a record move waits for a yes (issue 1126, ADR 0547 §2, §3) 02d9d7b053

jschoubben added 1 commit 2026-10-26 17:51:37 +00:00

Integration: a node the placement names composes and applies its own module with no controller composition, and again on a changed config value (issue 1126, ADR 0547 §2) e4dbb49d2f

jschoubben added 1 commit 2026-10-26 18:05:15 +00:00

The node's composer asks the vault's own for its modules' secrets sealed to its key, and keeps a value first had while its generation stands; two agent tests folded to hold the count (issue 1126, ADR 0550 §5) 2dc384d641

jschoubben added 1 commit 2026-10-26 18:16:35 +00:00

Pin mesh-sdk 4d5f430: the node's wants say it composes them (Self) (issue 1126) 1241ee7041

jschoubben added 1 commit 2026-10-26 18:21:26 +00:00

The node's composer asks the vault for the pair credentials its composition reads, as consumer and provider, sealed to its key (issue 1126, ADR 0550 §5) 1e38c42646

jschoubben added 1 commit 2026-10-26 18:24:39 +00:00

The node keeps the mesh's own certificate it applies, from its kept declaration at start, for its record; one agent test folded to hold the count (issue 1126, ADR 0555 §3) f8afaefba0

jschoubben added 1 commit 2026-10-26 18:26:27 +00:00

The node composes again when the vault says a secret changed, so a rotated secret or credential reaches it at once (issue 1126, ADR 0547 §2) bb46a6ad0f

jschoubben added 1 commit 2026-10-26 18:34:26 +00:00

The node agent begins again composing its own when the catalogue places its node, with no restart (issue 1126, ADR 0549 §4) 21d6583b5e

jschoubben added 1 commit 2026-10-26 18:40:44 +00:00

Pin mesh-sdk feat/1126-nodes-compose 9713c30: placement carries a settings-form module's values (issue 1126) cdd3f3fd4f

jschoubben added 1 commit 2026-10-26 19:09:44 +00:00

Review of L2: a node that cannot compose says so in each wanted module's have, failed, while it keeps what it runs (H2); the composer keeps the box the node runs when it opens to the vault's value, so neither the switch nor a restart moves a composition (H1); pin mesh-sdk 3968849, whose node asks the vault only for a module declaring a secret (H8's failure) (issue 1126) 58de6aa10a

mesh-tools changed title from WIP: The node agent writes its record in its own have key (issue 1126) to WIP: The node composes its own modules once the catalogue places it, and writes its record (issue 1126) 2026-10-26 19:13:17 +00:00

jschoubben added 1 commit 2026-10-26 19:23:18 +00:00

Review of L2, round 2: a refusal at the first compose after a start keeps what the module's have said runs (1); each have of a self-composing node carries the values its composition holds sealed, and the composer reuses them after a restart, so a rotated secret moves no composition at a restart (2); pin mesh-sdk dd9d9d5 (issue 1126, ADR 0547 §3) 4476e58080

jschoubben added 1 commit 2026-10-26 19:29:16 +00:00

Review of L2, round 3: a have written with no composition keeps what the module's last have said runs (fingerprint, digest, sealed values), for every writer; a record module run nothing of since the start judges its move against its last have and waits for a yes (issue 1126, ADR 0547 §3) 23d66187a8

jschoubben added 1 commit 2026-10-26 19:35:53 +00:00

Pin mesh-sdk feat/1126-nodes-compose 03dce12, the group's head: the checker refuses a pin that is neither trunk nor the group's head (issue 1126) 59d77dd457

mesh-tools marked the pull request as ready for review 2026-10-26 21:09:22 +00:00

jschoubben added 2 commits 2026-10-26 21:09:55 +00:00

Pin mesh-sdk 5f45175 (l2-next: feat/1126-nodes-compose merged with sdk main) after merging main (issue 1126) af2d2a2c14

Pin mesh-sdk 9796444 (l2-next: feat/1126-nodes-compose merged with sdk main #101, the standing-test race fixes) (issue 1126) 1d44288514

mesh-tools merged commit be94d2689e into main 2026-10-26 21:11:37 +00:00

mesh-tools deleted branch feat/1126-nodes-compose 2026-10-26 21:11:37 +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#149