Design 47 H: H-A-147, validate's base revision is pinned with the take-in

This commit is contained in:
2026-11-20 16:23:37 +01:00
parent 26f5505e39
commit 3e177edf69
@@ -712,3 +712,12 @@ Where two preparers disagreed, the chosen one is named.
failed is forgotten: the engine asks `versions` again at the next want, the next `compose` by hand, and after a
bound while the module is held, and says so in its journal; a resolution whose fetch succeeded is kept as today.
At this clean state a restart of the desktop's node-engine stands in once. P3.
- **H-A-147 (the base of validate's "before" case is pinned with the take-in, 16:26)** Met live at pipelines 13 and
15: the pin judge (§749, the removal of G-15 §579) removed the branch's previous revision in the very write that took
the next one in, because its own pipeline had ended and nothing else pinned it; validate (H-A-108, judged against
the branch's previous revision, read as the number before the candidate's) then could not run and the composition
was not asked. The indexer pins, in the take-in's write, the branch's previous revision (the newest it kept before
that write) for the same pipeline record as the take-in's own, and frees both with that record at the pipeline's
end; so validate's base stays as long as the pipeline that needs it. Not chosen: validate taking the newest kept
revision below its own, which would count every module moved since as altered and refuse problems the change did
not cause (ADR 0578 §2), a silent guess. P7, P12, P3.