From fa7709003d3b625eca96e63e3dc9531170d759d0 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 18:14:05 +0100 Subject: [PATCH] Design 47 H: H-A-176, what a cycle ends and how the pipeline then ends --- 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 7ee7affa..16140c30 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 @@ -920,3 +920,8 @@ Where two preparers disagreed, the chosen one is named. 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. +- **H-A-176 (what a cycle ends, and how the pipeline then ends, 18:14)** Met in the review of H-A-175: a cycle + ends not asked only the steps of the unplaced movers (the cycle's members and the movers that wait only on them), + never a step already asked; the why names only the edges whose two movers share a strongly connected group. The + pipeline then ends by the end judgement of H-A-163: a required step not asked counts as not passed, so it ends + failed as soon as no required step is still open, and steps already running run to their own end. P3, P7.