From 09cf7d609da7aef807c8682dee4dd327eff510c3 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:48:29 +0100 Subject: [PATCH] Answer A-430b: a branch build is named by the version the builder reserved; build.ended carries it and the registry tags it unreleased --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 08cf63a9..43dfbf48 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1149,3 +1149,11 @@ the principle that settles it, cited as "design 47 G A-n". verb `versions` with the artifact's registry name `/`, and fetches the bytes as today over the artifact store by the digest that answer gives; an image is pulled by name and version. The node-engine's manifest invokes those `versions` verbs; no registry verb is added. +- **A-430b** (A-430a, §52, §53, §371; principles 7 and 8) The version a build of another watched branch is numbered + under is the one the builder reserved when its build started (§52), never released: `build.ended` names it as + `version` for every build that reserved one, and the registry seat that holds each artifact tags a branch build's + artifact at that reserved version without releasing it, so the node-engine resolves it through `versions` like a + released one. §371's and §53's "stored by digest with no version" becomes "tagged at its reserved version, + unreleased"; the `package-published` comparison by digest stays. Order within G: the node-engine's resolution by + version first (it unblocks every released build), then the builder and registry tagging; until those land, a want + for a branch build keeps its digests for a node whose node-engine reads them, and that form goes with them.