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 e07b5ce9..b025dbc9 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 @@ -1728,3 +1728,13 @@ the principle that settles it, cited as "design 47 G A-n". holds for a test run. - **A-470** (G-24 A4, R2; A-468b; principle 8) The second bound key of a run is `untaken.`, beside §720's `bound.`, in `composition-runs` and in `test-runs`. +- **A-470a** (G-24 R2; §725, §330; principle 7) The ager reads a test run's key from the step-log entry's pipeline (its + step's `shared` run) and ages `test-runs` in the same pass, before §330's 7-day retention deletes that pipeline; + `test-runs-kept`'s maximum is 7 days (168h). No field is added to the step log. +- **A-470b** (G-24 H2, A3; §721, §722; principle 3) A module named in `blamed` with the words "not tried: the search + reached its bound" was never shown at fault: the assigner judges it `could not run` for that machine in that module's + composition step, naming the bound, never `failed`. +- **A-470c** (G-24 H1, H2; §721, A-468l, A-469j, A-469k; principle 7) As built: a hold ends the problem when the retry + 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.