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 d3fb911a..7350e455 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 @@ -721,3 +721,12 @@ Where two preparers disagreed, the chosen one is named. end; so validate's base stays as long as the pipeline that needs it. Not chosen: validate taking the newest kept revision below its own, which would count every module moved since as altered and refuse problems the change did not cause (ADR 0578 §2), a silent guess. P7, P12, P3. +- **H-A-148 (an assignment no watched branch lists does not fail the machine's composition, 16:28)** Met live: the + retired checker's assignment on the control-node makes every composition there refuse "nothing provides", so every + pipeline's composition step on that machine ends could not run; the module assigner's `propose` to take it off is + refused because its own picture lacks the apps on the other watched branches (the same fault as H-A-143, in the + module assigner: a finding for H2). A module assigned to a machine that no watched branch lists is left out of the + composition's assignments as well as its manifests, said in the reason as unlisted (H-A-143), and raised as a + condition on the assignment, never as the machine's failure: a stale assignment is a fault of the assignments, not + of the change under judgement (ADR 0578 §2). A module the catalog lists with no registration (the wireguard module + today) is registered through the catalog's verb; until then it is unlisted by H-A-144 and left out alike. P3, P7.