Answer A-470p: a run's end comes before every other act of its step-ended

This commit is contained in:
2026-11-17 12:32:55 +01:00
parent 83fab59cac
commit 42e9484261
@@ -1787,3 +1787,6 @@ the principle that settles it, cited as "design 47 G A-n".
and the run (taken for `bound.`, untaken for `untaken.`) has no end; with bounds armed by compare-and-set for the run's
own ask this gives the same result, and no field is added. A run's end is written when its `step-ended` is heard,
before any finding the step says, so no wait elsewhere delays it past its bound.
- **A-470p** (G-24 A4; A-470o, A-465a; principle 3) A-470o holds for every other act a `step-ended` handler does, not
only findings: the assigner ends the run first and deletes the kept input after; when the delete fails the event is
asked again, and its redelivery finds the run ended (said as ignored for the run) and still deletes the input.