Answer A-413: named asks are unused only while no account the part composes may publish one
This commit is contained in:
@@ -1003,3 +1003,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
- **A-412a** (A-412; principles 1 and 7: the form of a seat's entry is its contract's) Both readings of an entry's
|
||||
manifest digest (the entry's form and the bare one) move into the seat `mesh-catalog`'s contract package; the indexer
|
||||
and the builder use them from there, and neither keeps its own.
|
||||
- **A-413** (§544 as G-12 answered it, A-170, A-231; live, the bus 2026-11-14 23:49: the builder of G asked 113 builds on
|
||||
`accept.delivery.<asker>`, and no named worker exists to take them, since the grants part counts named asks unused while
|
||||
no entry of the revision invokes a build seat's queue, and in the start no entry of G is in the revision yet; principles
|
||||
3 and 2) Named asks are unused only when no entry of the revision invokes a build seat's queue and no account the part
|
||||
composes is granted to publish a named ask; while either holds, each build seat's queue keeps its named worker, made at
|
||||
the part's next pass. The purge at a revert stays as §544 says, for a revision whose accounts ask no named ask.
|
||||
|
||||
Reference in New Issue
Block a user