Answer A-426 (an acting wait ends on any running build that serves the edge) and A-427 (a put may hold the running build)

This commit is contained in:
2026-11-15 15:56:51 +01:00
parent 8abbb539fd
commit b20b382cd9
@@ -1104,3 +1104,12 @@ the principle that settles it, cited as "design 47 G A-n".
its data), set at mesh level with `mesh-config.config`; its default is A-425's: `take-off`, `remove-node`, `stops`.
A proposal none of whose changes is listed is applied at once. The asks of a module whose moves a person takes stay
as they are. A change of the key is said in the assigner's log at its next pass.
- **A-426** (§268, A-323, A-330; live, the build node and ace 2026-11-15 15:52-15:56: the pipeline's want on novox
waited for an assigner build not yet built, while a working assigner ran, and only a hand release moved it; the
operator: "then our design is stupid"; principles 2, 3 and 7) An acting wait waits only while its acting part runs
nothing that serves the edge: an acting part that runs a build serving the edge's seat or verb ends the wait at
once, whatever version its newest is, and the wait says which build it took. A wait on a version not yet built is
never held for that alone. (This replaces the node-engine exemption of A-323 and A-330 with a rule for every part.)
- **A-427** (A-426; live: the builder refuses a put of a version it did not build, so a part started by hand cannot be
held, and the trunk's newest build of it would replace it; principles 2 and 4) A put may name the build a node
runs now, read from the node's running statement, and holds the want there; the builder's store is not asked for it.