From 72fab0f717bd48486a90e36d3c4a1079a385231d Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 17:39:19 +0100 Subject: [PATCH] Design 47 H: H-A-284, the kept mover's steps and its entry's revision --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 8 ++++++++ 1 file changed, 8 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 5df3d1bd..087b12ed 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 @@ -1628,3 +1628,11 @@ Where two preparers disagreed, the chosen one is named. of its own for such movers. Only a revision of a new source (a merge) moves movers. Until the indexer re-pins once per release (owed, H2: pins from the reservation, confirmed at publish), this holds the pipeline steady. In the runner. ADR 0682 (one take-in, one pipeline), P7. +- **H-A-284 (the kept mover's steps and its entry's revision, 17:39)** Amends H-A-283. (1) When a same-source re-pin + moves a kept mover's fingerprint, every step of that mover, open or ended, is ended superseded and placed again + from the re-pin revision's entry, the build first; no step stands for a fingerprint the pipeline no longer + delivers. (2) The pipeline keeps, in its own state beside the movers (not in the seat's Mover form), the catalog + revision each kept mover's fingerprint is from; the pin check and the placing read that mover's entry and pins at + that revision where set, else at the pipeline's; the build ask keeps naming the pipeline's revision (the builder's + routing) and carries the pins of the mover's entry as every ask does (H-A-203). P3, P7 (no contract change for a + runner-internal fact).