Answer A-430b: a branch build is named by the version the builder reserved; build.ended carries it and the registry tags it unreleased

This commit is contained in:
2026-11-15 16:48:29 +01:00
parent 547eec3373
commit 09cf7d609d
@@ -1149,3 +1149,11 @@ the principle that settles it, cited as "design 47 G A-n".
verb `versions` with the artifact's registry name `<module>/<artifact>`, 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.