diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 14df27ee..7ee7affa 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -913,3 +913,10 @@ Where two preparers disagreed, the chosen one is named. were not written; freeing their older release on the tier-late event would remove the revision their want names. A `pipeline-wanted` with outcome tier-late frees nothing; the same pipeline's later `pipeline-wanted` with outcome running frees as H-A-173 says. P2, P7. +- **H-A-175 (a cycle among a pipeline's unplaced movers ends it failed, 18:09)** Met at main.28 and main.30: a + build module's toolchain edge into the movers it is built from made the runner wait per mover on both sides (G §270 + and A-326 settle that case: what a build module is built from is built by its running version, never waited for); + a cycle that rule does not break left the pipeline running with journal lines only, since §745's refusal lives in + validate, which is asked only for a placed mover. The placing ends a pipeline failed with why `cycle`, naming each + artifact and edge kind, as soon as every unplaced mover waits only on unplaced movers, each of their steps ended + not asked (as H-A-101 (2) does). P3, P7.