From 72bc73df27829ab754fc45dd8a27527ecd1ae532 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 12:24:05 +0100 Subject: [PATCH] Answer A-470n: a run's bound names its ask, so a replaced run's late signal ends nothing --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 1c5f902f..c6472ee1 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 @@ -1778,3 +1778,7 @@ the principle that settles it, cited as "design 47 G A-n". reader's step said its end, written when it does and carried with the reader into a rerun's run; a take-up says `step-ended` only for a reader with no `ended`, or one marked `rerun`, so a carried reader that passed is told from a step that joined the rerun's run later, from the key alone. +- **A-470n** (G-24 A4, R2; §720, §725; principles 3 and 2) A run's `bound.` and `untaken.` keys hold the run's `ask`: + an `ask-taken` or `step-progress` arms or renews a bound only when its ask is the one the run's key names, written by + compare-and-set, and an expiry ends the run only while the run's key still names that ask; a late signal of a run + that was replaced moves nothing and is said in the journal. The same holds for the runner's `test-runs`.