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 ea645643..ba69af53 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 @@ -888,3 +888,10 @@ Where two preparers disagreed, the chosen one is named. (the seat mesh-wants' event, said once when a pipeline's wants are written to the end, tier-late included), for each module the newer revision's movers name. The indexer consumes that event (its manifest says so). A revision a release pin holds keeps its entries as today. P1, P2, P7. +- **H-A-171 (a mover waiting on a publish, at the end judgement, 17:45)** Met in the review of H-A-163: a mover + with no step may also be one that waits for the publish of a mover it builds on (its dependency's build passed, the + package-published not yet heard). The end judgement tells the two apart by the registration lookup: a mover the + registrations do not name waits on its registration, every other unplaced mover waits on a publish. Both hold the + end while every placed mover's required steps passed; as soon as one failed or could not run and none is open the + pipeline ends failed, and the why names each unplaced mover with its own reason (" has no registration", + " waits on the publish of "). P3, P7.