The node-engine publishes each placed module's data items, so disk-load stops recomposing the node (ADR 0577) #191

Merged

mesh-tools merged 3 commits from feat/data-items into main 2026-11-01 00:03:19 +00:00

Conversation 1 Commits 3 Files Changed 10

+579 -19

3 Commits

Author	SHA1	Message	Date
jschoubben	e031758e4a	Forget a kept build when its key is written again, and retry data items on the composer's bound (review round 1) ... The builder claims a done key again as a new revision, so a build kept as done is dropped on any write of its key. Data items that could not be worked out or written stay due and owe a pass after the growing bound, so a first write refused before the state or grant exists is tried again without waiting for an unrelated composition. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 00:27:29 +01:00
jschoubben	122f4dd727	Read a done build once, and work out the data items in the scope the pass composed in (ADR 0577) ... The data items after a pass re-read each placed module's build over the bus (about 55 per pass on ace, g14 and shanks); a done build never changes, so the composer keeps it. The items are now worked out with the pass's own kept builds and modules run inside the node's own, as composed. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 00:18:30 +01:00
jschoubben	e0261cdfc1	Keep each placed module's data items in the engine's state data, so disk-load measures without composing (ADR 0577) ... After a pass that handed a new composition, the node's composer works out its modules' data items from the inputs it composed from and writes each module's key <node>.<module> of mesh-host_data only when it differs, deleting the keys of modules that left. Pins mesh-sdk feat/data-items for the contract and the engine's grant. Two tool-answer tests are merged so the unit count stays where it was. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 00:09:25 +01:00