mesh-grants takes the grants of the node-engine's data items (ADR 0577) #128

Merged
mesh-tools merged 1 commits from feat/data-items into main 2026-11-01 00:03:17 +00:00
Member

Delivery group feat/data-items (mesh-sdk, mesh-host, mesh-catalog, mesh-delivery), one check, one Approve. Decision: ADR 0577 (the node-engine publishes each placed module's data items; disk-load watches them and composes nothing), changing ADR 0571 §5. Fixes issue 1955 in part: disk-load needed 30 to 45 minutes per round on ace, g14 and shanks, and went silent for 45 hours when its mesh-sdk refused a manifest.

Quick fix (a prefix filter in the states reader) not chosen: a fourth hand pin and more logic in mesh-sdk. Thorough fix chosen: one composer per node, disk-load event-driven.

This member: modules/mesh-grants pins mesh-sdk c28c645 only, so the engine may write mesh-host_data and disk-load may read it; it takes in nothing else from mesh-sdk.

Reviewed-by: reviewer-577@shanks at ddadb75bf4
Pushed-by: builder-577@shanks

https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

Delivery group feat/data-items (mesh-sdk, mesh-host, mesh-catalog, mesh-delivery), one check, one Approve. Decision: ADR 0577 (the node-engine publishes each placed module's data items; disk-load watches them and composes nothing), changing ADR 0571 §5. Fixes issue 1955 in part: disk-load needed 30 to 45 minutes per round on ace, g14 and shanks, and went silent for 45 hours when its mesh-sdk refused a manifest. Quick fix (a prefix filter in the states reader) not chosen: a fourth hand pin and more logic in mesh-sdk. Thorough fix chosen: one composer per node, disk-load event-driven. This member: modules/mesh-grants pins mesh-sdk c28c645 only, so the engine may write mesh-host_data and disk-load may read it; it takes in nothing else from mesh-sdk. Reviewed-by: reviewer-577@shanks at ddadb75bf474a2cd9c0ce981e4d94d394d154335 Pushed-by: builder-577@shanks https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
mesh-tools added 1 commit 2026-10-31 23:46:33 +00:00
mesh-grants pins mesh-sdk feat/data-items, so it grants the node-engine's data items state (ADR 0577)
mesh/delivery merged: source.main moved to novox/mesh-delivery@b1f262d7d06e
mesh/delivery-group group feat/data-items merged: every member is merged
mesh/check pass ddadb75bf474 on 91128d4f0af6 | unit 4510 run, 4259 kept, 49 skipped | integration 4589 run, 4361 kept, 51 skipped | over bound: unit, …
ddadb75bf4
The only change taken in is ADR 0577's: each node's engine writes its own keys of mesh-host_data,
and each node's disk-load reads its own node's keys alone. Without it the engine's writes are
refused and disk-load measures nothing.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
Author
Member

Delivery novox/mesh-delivery@ddadb75bf474 — merged since 2026-11-01T00:03:18Z

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

Group feat/data-items: novox/mesh-catalog@0c46f47ae5, novox/mesh-delivery@ddadb75bf4, novox/mesh-host@e031758e4a, novox/mesh-sdk@c28c645ca4

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

Transitions

  • 2026-10-31 23:46 (new) → proposed (announced): novox/mesh-delivery#128's head announced
  • 2026-10-31 23:46 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-01 00:03 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-delivery@ddadb75bf474` — **merged** since 2026-11-01T00:03:18Z **Source** — source.main moved to novox/mesh-delivery@b1f262d7d06e. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/data-items`: novox/mesh-catalog@0c46f47ae57e, novox/mesh-delivery@ddadb75bf474, novox/mesh-host@e031758e4a37, novox/mesh-sdk@c28c645ca406 - composed together: pass — the checker's verdict at the members' heads (e2b935f1f425) **Transitions** - 2026-10-31 23:46 (new) → proposed (announced): novox/mesh-delivery#128's head announced - 2026-10-31 23:46 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-01 00:03 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 merged commit b1f262d7d0 into main 2026-11-01 00:03:17 +00:00
mesh-tools deleted branch feat/data-items 2026-11-01 00:03:17 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#128