5 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	97a2d841c7	Land feature 57's controller work on its release branch ... The controller plans config, templates and moved providers' provisions, hands bus accounts to the vault and judges the new manifest words, on the feature's SDK and node-engine validator (feature 57, config and provisioning).	2026-10-15 21:27:33 +00:00
jschoubben	c3946e5d72	Pass the node-engine and resolver on their third reading, at most two minutes ... The operator wants these gates as fast as they can be: counting readings only after two minutes added about 80 s to every node-engine rollout for no safety. Count from the send, pass on the third healthy reading, and pass a module healthy at every reading at two minutes on what it has (novox/hq ADR 0352).	2026-10-13 22:55:46 +02:00
jschoubben	524295926f	Pass the controller's first-node gate on one reading after the witness window ... The controller runs on one machine, so three readings over two minutes guarded no other machine and held every walk behind it. Judge each module by its own rule: one reading for the controller and the tool runner once the node-engine's witness window has ended, one for mesh-delivery, three for the node-engine and the resolver with the first two minutes after the send (novox/hq ADR 0351). The gate's verdict names the rule it applied.	2026-10-13 22:39:32 +02:00
jschoubben	ad3b4f185b	Judge a leaf module on one healthy reading, a core module on three (hq issue 524) ... ADR 0282 decided readings by class and ADR 0304 took a leaf module to one, but the gate never learned it: every build, leaf or core, needed three readings over at least two minutes, so a container module that was healthy at once still waited about two and a half minutes on its first machine. The number of readings and the settle time now follow the module's class: three after two minutes for the controller's own path and the resolver, one for every other module. Tests that judge a gate's other rules keep leaf modules on three readings.	2026-10-12 01:08:14 +02:00
jochen	2bfa6ae4a0	No build reaches a machine without a gate; a release plan walks what waits (hq ADR 0236) ... A send carries the machine's whole declaration, so at the switch to roll the next send of anything would have carried the old default's backlog, unjudged, to every machine. A gated send now carries and judges everything waiting on its machine; every other send is refused or leaves the machine; a release plan walks what waits one machine at a time, the control node last, and one that fails holds the next until a person releases it.	2026-10-06 19:14:25 +02:00