mesh-delivery

Files

T

jschoubben 73582f92e1 Assigner: the node-engine's want first; the acting-wait check sees cycles across steps

The assigner and the node-engine on one node waited for each other for ever: the assigner's
want in step compose for the new node-engine, the node-engine's in step place for the new
assigner, and the cycle check counted one step at a time, so nothing said it. The node-engine's
own want (the holder of the seat node-engine on the node, read from the acting edges' seat) is now
held by no acting edge, so it is written first and the node's other wants, the assigner's own
included, wait for it. Cycles finds a cycle across steps as well as within one, and a want held
on a cycle no rule breaks is the finding acting-cycle (scope module, id <node>.<module>), naming
each edge's step, cleared by the next pass that finds it on none.

Builds: design 47 G §49, §268, §272, A-323, A-330

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

2026-11-13 01:56:48 +01:00

candidate.go

AS12: the assigner keeps a run's candidate assignment graph, dropped on the run's group-ended

2026-11-12 09:14:45 +01:00

compute.go

Assigner: the node-engine's want first; the acting-wait check sees cycles across steps

2026-11-13 01:56:48 +01:00

cycle_test.go

Assigner: the node-engine's want first; the acting-wait check sees cycles across steps

2026-11-13 01:56:48 +01:00

cycle.go

Assigner: the node-engine's want first; the acting-wait check sees cycles across steps