From 976f2942ad5fb854e8477f77d37eb7482bb83c05 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 23:48:33 +0100 Subject: [PATCH] Design 47 H: H-A-217, every recompute that moves a fingerprint keeps a revision --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 7 +++++++ 1 file changed, 7 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 873ac735..24a1c95d 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 @@ -1191,3 +1191,10 @@ Where two preparers disagreed, the chosen one is named. the source the pipeline-ended event names in its kept value for the pipeline (its tier progress) and sends it in pipeline-wanted beside the revision; a kept value from before the field is read with source = the key's number, as it was. P1 (the source is the gate's truth, carried, never derived). +- **H-A-217 (every recompute that moves a fingerprint keeps a revision, 23:48)** Met in the build of H-A-213: three more + whole recomputes (on a build module's assignments change, on a toolchain report, by the recompute tool) still moved + fingerprints with no kept revision, against H-A-211. Any recompute that moves at least one fingerprint keeps the + branch's next revision with the moved modules as movers, `call-kind` recompute and `call` naming its reason + (assignments, toolchain, by hand); one that moves none keeps nothing. The runner treats every revision whose kind + is not take-in alike: one pipeline for its movers (H-A-213 (2)). A module accepting a series takes the series' + newest at the release's re-pin (H-A-204), which is the only publish that moves it. P1, P4.