From 42e9484261dbe26d85361a0626144885a437a457 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 12:32:55 +0100 Subject: [PATCH] Answer A-470p: a run's end comes before every other act of its step-ended --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4bd5b0c1..9b1eeafd 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -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. -- 2.54.0