Answer A-417: a registry holder tags a version on the artifact it holds by digest, else takes it from the artifact store

This commit is contained in:
2026-11-15 02:37:16 +01:00
parent 39ab7efb6b
commit 2ce9268504
@@ -1036,3 +1036,12 @@ the principle that settles it, cited as "design 47 G A-n".
registry seat's holder from the seat-holders reading A-298 names (`SeatHolders` of the catalog client), the one its
FollowSeat of the assignments already takes, read from its start. Its manifest and grants do not change. A-416 is
read with "the SDK's FollowSeat" as this reading.
- **A-417** (A-73, A-50, §588; live, the control-node 2026-11-15 01:57 and 02:28: the build node's publish of
mesh-delivery-pipeline 0.1.6 stores each artifact untagged, as A-73 has it, and the registry holds it, under the
artifact digest the builder reserved; the builder's publish of the version with that digest and no parts is then
refused, since the holder of `oci-artifact-registry` says published only for a tag it already holds and otherwise
opens a transfer with no parts; principles 3 and 7) A registry holder given a publish with a version, a digest and no
parts tags that version on the manifest it holds of that artifact digest under the name, and says published; when it
holds none, it takes the bytes from the artifact store by that digest, as A-73 and A-50 say, and stores and tags them;
when neither has it, it refuses as not stored, naming the digest. The builder's publish again names its transfer in
the transfer form the build's own step uses.