Answer A-470d and A-470e: a rerun carries every reader with its mark, and a newer run is told by its ask

This commit is contained in:
2026-11-17 11:39:20 +01:00
parent 12b7e246e4
commit 520e95a10c
@@ -1738,3 +1738,10 @@ the principle that settles it, cited as "design 47 G A-n".
composes or fails with other words (the rule `culprit` uses); path pairs are blamed only for a module the change newly
refuses; with no `ComposedHow` every placed module counts as changed; `blame_tries` counts the retries after the first
composition.
- **A-470d** (G-24 A6, R5; §727, A-468g; principles 3 and 2) A rerun's new value carries every former reader: each
that did not pass with `rerun` true and `by` the rerun's caller, each that passed with `rerun` false. At the new run's
end exactly the readers marked `rerun`, other than the rerun's own step, say `step-ended` again, marked rerun with that
`by` and naming the new run's ask in `shared`; the marks are in the key, so a restart takes them up. The same holds for
a test run's readers.
- **A-470e** (G-24 R5, A-469l; principle 8) A run's key is the same string before and after a rerun replaces it, so "an
end naming a newer run" is one whose `shared` `ask` differs from the ask the step last read.