Answer A-415: a published heard before the build's digests is kept on its reservation and marks it when the digests land
This commit is contained in:
@@ -1016,3 +1016,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
the catalog entry of the build its want says is being built (the newest of its first watched branch), read through the
|
||||
seat `mesh-catalog`'s `entry` as any entry, for its account's grants, membership and seat traffic alone. A want that
|
||||
names no newer build leaves its membership carried as today, said once.
|
||||
- **A-415** (§588, A-73; read from the code 2026-11-15 by the developer, the live proof waits on its new log lines: the
|
||||
builder records a trunk build's digests on its reservation only after the build's claim is finished, while the registry
|
||||
publishes during the build, so a registry seat's `published` heard before then marks nothing, is acknowledged and is
|
||||
lost, and package-published is never said, as for 0.1.6; principles 1, 3 and 7) A `published` that marks no artifact
|
||||
of its reservation yet is kept on that reservation, in the builder's own kept state, as heard (name, version, digest);
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user