Answer A-470q and A-470r: an end said again has its own message id, and a drop ends only the ends owed

This commit is contained in:
2026-11-17 13:03:28 +01:00
parent 7f846906ee
commit cd3428755a
@@ -1790,3 +1790,10 @@ the principle that settles it, cited as "design 47 G A-n".
- **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.
- **A-470q** (G-24 review r1, assigner; §727, A-470d; principles 3 and 8) A composition step's first `step-ended` keeps
the message id `<ask id>`; an end said again is published under `<ask id>.<ask of the run whose end makes it say
again>` (the moved run for a move, the open run it is taken up from for a take-up, the dropped run for a drop), so
the bus's deduplication never drops it. The same holds for the runner's ends said again.
- **A-470r** (G-24 review r1, assigner; §728, §727, A-470m; principle 3) A drop ends `could not run`, naming the drop,
each reader whose end is owed (no `ended`, or marked `rerun`), once each, and ends the run without moving its other
readers; a reader that ended passed keeps its verdict.