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 ad74d656..f239e7ce 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 @@ -1141,3 +1141,13 @@ Where two preparers disagreed, the chosen one is named. requirements of every module of the repository, on every watched branch holding it) and recomputes the modules state, exactly as a publish re-pin does; a moved fingerprint reaches the runner by the same path and event a re-pin's does, and gets its pipeline the same way; the gate is not asked and the revision numbering is untouched. P1, P4. +- **H-A-211 (a re-pin is taken in as a catalog revision of the same source, 23:14)** Met in the pin specification + (H-pins-spec-and-gaps, gap 1): a re-pin on a publish only changed the first watched branch's picture in memory; the + re-pinned module was never a mover, its new fingerprint had an entry in no kept revision (the live "entry-missing" + holds on wants), and other watched branches were never re-pinned. A catalog revision already carries its source as a + separate field (revision N of source S; today N equals S by habit). A re-pin keeps the next revision of the branch + (N+1) with the same source S, its movers the re-pinned modules, said as take-in.taken with a call of the form + "publish of ", on every watched branch holding them; the runner keys a pipeline and its "waits for + revision" by the revision number, never by the source (a no-op where they were equal); the take-in again of + H-A-210 is kept the same way (its call "take-in again of "). H-A-210's "no revision" is amended so. + P1 (one truth: every fingerprint has its entry in a kept revision), P4.