Design 47 H: H-A-252, a validate end is matched by its ask alone and ends every mover's validate step

This commit is contained in:
2026-11-21 11:48:17 +01:00
parent cfeee0cf1d
commit e3db5eed6d
@@ -1440,3 +1440,11 @@ Where two preparers disagreed, the chosen one is named.
- **H-A-251 (the tool runner binds a state once, not on every read, 11:47)** Met live: the tool runner's state get
binds the bucket (a stream-info request) before every get, doubling every read on the bus. The runner keeps one
binding per state for the process (re-bound on a bind error), so a read is one answer. In mesh-tools. P7.
- **H-A-252 (a validate end is matched by its ask alone and ends every mover's validate step, 11:48)** Met live, the
second of the kind of H-A-236: the pipeline's one validate ask names no mover (H-A-51), the holder's end names
the mover whose body it took, and the runner compares that mover with the first step carrying the ask and drops the
end when they differ ("a step's end the runner does not take"), so a validate that passed was never taken, every
mover's validate stayed running and the pipeline held the slot (main.88 at 11:40, main.76 before it). The runner
matches a validate end by its ask id alone and ends the validate step of every mover the pipeline moves or has
moved under that id, with the end's outcome; the same for the composition's shared runs where one ask serves many.
The kind: a shared ask is never read as one mover's. P4, P7.