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 c6472ee1..4bd5b0c1 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 @@ -1782,3 +1782,8 @@ the principle that settles it, cited as "design 47 G A-n". 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`. +- **A-470o** (G-24 R2, A4; A-470n; principles 7 and 3) A bound's expiry reaches its owner with no value, so A-470n's + expiry clause reads: an expiry ends the run only when its `bound.` or `untaken.` key is still absent when read again + 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.