From 9c61151f1f6bff3dff9073f14002e543e446a37b Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 21:29:44 +0100 Subject: [PATCH] Design 47 H: H-A-192, the builder never computes a pin --- 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 33b3eee9..0b827f53 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 @@ -1019,3 +1019,11 @@ Where two preparers disagreed, the chosen one is named. - **H-A-191 (list's counts, 21:19)** Met in the build of H-A-189: the Pipeline value gains two optional integers, `mover-count` and `step-count`, that `list` alone sets, answering each record with `steps` empty; `show` keeps the steps; readers of list that use keys and outcomes see no change. P4, P7. +- **H-A-192 (the builder never computes a pin, 21:29)** Met live in the builds of the engine's carrier: the builder's step + path, waiting for a package of the same pipeline, pinned it at the module's release number ("v" + release), and the + Go build module, given no pin, took the version of another package of the same repository; both built against + versions never published. The builder takes a package's pin from the catalog entry alone (H-A-183: the registry's + published version of the package path within the accepted series) and, where the entry names none, waits for the + registry seat's package-published event of that path and series (H-A-165) and pins the version that event carries, + never a number it derives; a build module given no pin refuses the build, loud, never takes another path's version. + P1, P4, P7.