Design 47 H: H-A-217, every recompute that moves a fingerprint keeps a revision

This commit is contained in:
2026-11-20 23:48:33 +01:00
parent eb433bfcd6
commit 976f2942ad
@@ -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.