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 04b8478f..08cf63a9 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 @@ -1141,3 +1141,11 @@ the principle that settles it, cited as "design 47 G A-n". tags it, and the registry's answer is what it applies. §379's digests in the want, and the assigner's check whether a node's node-engine reads them (`want-parts`), go. A build of another watched branch, which has no released version, is named by the version the builder numbered it under. +- **A-430a** (A-430; principles 7 and 8) Every build a want names has a version: a released trunk build its released + version, a build of another watched branch the version the builder numbered it under (A-430), and a kept build its + numbered version with `kept-on` naming the node that keeps it (§526); a want never names a fingerprint's artifacts + or digests. The node-engine resolves each artifact the catalog entry names at that version through the seat that + holds its kind (`oci-artifact-registry` for a bundle or archive, `container-image-registry` for an image), by its + 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.