ADR 0096: an upstream image is copied between registries; issue 046 resolved; design 18 amended

2026-09-21 20:43:07 +02:00
parent 39a01b7f7e
commit 8d981e21b1
5 changed files with 85 additions and 6 deletions
@@ -1,9 +1,9 @@
 ---
-status: located
+status: resolved
 opened: 2026-09-14
 located-in: [mesh-controller internal/builder (upstream artifacts)]
-fixed-by:
-amended-design:
+fixed-by: ADR 0096; mesh-controller multiple-fixes (the builder copies the index and its manifests between registries over the registry API); proven by a test against a fake upstream serving an index over two platforms
+amended-design: 03-DESIGN/01-to-be/18-building-a-module.md
 ---

 # 046 — An upstream image cannot be mirrored into the mesh's own registry
@@ -12,6 +12,8 @@
   than a limitation; today every machine on one mesh is the same architecture, and that
   assumption is now written down here rather than nowhere.

-**Located in:** the builder's upstream-artifact step. Not fixed here: a registry-to-registry copy
-is a few hundred lines against the registry API and is proven only against a real registry
-serving a real index, which is a lab run of its own.
+**Located in:** the builder's upstream-artifact step. Fixed as
+[ADR 0096](../../02-DECISIONS/0096-an-upstream-image-is-copied-between-registries.md): a copy over
+the registry API, proven against a fake upstream serving an index over two platforms behind a
+bearer challenge. A run against the public hub from a mesh's builder is the remaining proof, and
+the first build of a module with an upstream artifact will be it.