ADR 0097: an undeclared base is said, not yet refused

2026-09-21 20:48:19 +02:00
parent 71072e240d
commit 43ca9ce0ae
2 changed files with 14 additions and 7 deletions
@@ -31,10 +31,15 @@ named it directly and the build worked when the public registry answered, which
 A build's `on` entry is either a module's artifact or an image published elsewhere, pinned by
 digest, read from one build argument. Before the build the image is copied into the mesh's
 registry under the module's repository and the recipe is handed the copy; genesis, with no
-registry, pulls it into the first machine's store. A recipe whose `FROM` or `COPY --from` names a
-registry image the manifest did not declare is refused before the build, naming the image and
-the remedy; its own stages, declared arguments and `scratch` are not fetches. An unpinned vendor
-image is refused: a tag is what somebody else can move.
+registry, pulls it into the first machine's store. A recipe whose `COPY --from` names a registry
+image the manifest did not declare is refused before the build, naming the image and the remedy;
+its own stages, declared arguments and `scratch` are not fetches. An unpinned vendor image is
+refused: a tag is what somebody else can move.
+
+A recipe whose `FROM` names an undeclared base is **said, not yet refused**: the mesh's own images
+— the control plane's, the builder's, the tool runtime's — start from a public base and declare
+none, and refusing those refuses genesis. They declare their bases next; until then every build
+names the undeclared base and the remedy.

 The package half of the issue is not decided here: the mesh's package registry already proxies
 the public one, and the failure the report saw has to be run again to be placed.