From fabb927f266c5373fda2144490f5fd37933956d5 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 04:08:33 +0100 Subject: [PATCH] Design 47 H: H-A-107, the pipeline keeps the movers superseded out of it Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 3 +++ 1 file changed, 3 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 534df897..cfb8ebbd 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 @@ -459,3 +459,6 @@ Where two preparers disagreed, the chosen one is named. bound, since it asks nothing new but its end; "waiting on its approval step" means every step not ended is an approval asked of the operator. P3. (c) `pipelines-stalled` and `queue-full` have the kind as their id, severity warning, no owner (the operator's), like `pipeline-failed`'s writer. P8. +- **H-A-107 (runner developer, 04:09)** The pipeline value keeps `superseded`, the modules a newer queued take-in took out + of it (written with the movers by compare-and-set; a C-R5 field of the seat, the contracts' writer); at the pipeline's + placing the runner writes a mover's build-step why from it (H-A-53). P1, P4.