The controller passes its first-node gate on one reading (ADR 0351) #310

Merged

mesh-admin merged 4 commits from feat/351-the-controller-passes-on-one-reading into main 2026-10-13 21:14:27 +00:00

Conversation 6 Commits 4 Files Changed 11

+619 -103

4 Commits

Author	SHA1	Message	Date
jschoubben	675466a8c3	Hold the store tests' modules as the settle time did, and fault a dip after any healthy reading ... Two tier tests relied on the two-minute settle to keep a module unjudged; the witness window and the gate's spacing now hold it. A healthy reading taken before the controller's floor counted no pass, so a dip after it did not take the two-minute pass away (novox/hq ADR 0352 decision 3).	2026-10-13 23:07:15 +02:00
jschoubben	41eefc2f8c	Test that a healthy node-engine passes at two minutes on one reading	2026-10-13 22:58:37 +02: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