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 905941c0..fcc1116e 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 @@ -1024,3 +1024,10 @@ the principle that settles it, cited as "design 47 G A-n". when the build records its digests, each kept `published` whose digest matches marks its artifact and package-published is said then, in the same way as for one heard after. Nothing asks the registry; a kept `published` whose digest never matches is said in the builder's log when the build records its digests. +- **A-416** (§588, A-302, A-415; live, the build node 2026-11-15 02:02 and 02:16: `builder_publish_again` for + mesh-delivery-pipeline 0.1.6 queued nothing, "no module running that claims the registry seat oci-artifact-registry + is known to the builder since its start", since the builder learns a registry seat's holder only from node-engine + `running` events heard since it started, and that knowledge dies with every restart; principles 1, 4 and 7) The + builder knows each registry seat's holder through the SDK's FollowSeat, as A-302 has the indexer follow its seats, + from its start; a `running` heard still queues the versions waiting on that holder, as §588 says, but is no longer + how the holder is known. A publish again whose seat has no holder said by FollowSeat says so, naming the seat.