From 6fe6d93fed33f414ce617f324a3a3197436837d9 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 19:03:53 +0100 Subject: [PATCH] Design 47 H: H-A-179, the composition step of a module no machine holds --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) 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 52e05bca..e9c1b458 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 @@ -939,3 +939,8 @@ Where two preparers disagreed, the chosen one is named. is placed, so the point is asked as before and a missing answer holds the move (never a move on a guess, P3); and the finding `restore-point-missing` is keyed by scope, id and kind across the mesh, so its id is `.`, as the engine's held findings are keyed, never the module alone. P3, P7. +- **H-A-179 (the composition step of a module no machine holds, 19:03)** Met at the second proof (main.35, + 19:00): mesh-delivery-sdk, a package module, has a required composition step, and no node places it, so the step + ended could not run ("no node places mesh-delivery-sdk on the branch main") and the pipeline can never pass. A step + with nothing to judge ends `nothing to run`, which counts as passed (ADR 0682 ยง8): the composition step of a mover + that no machine holds on the branch ends so, saying why, as the levels of an archive artifact do. P3, P7.