Answer A-416a: the builder reads a registry seat's holder from the catalog's seat holders, not FollowSeat
This commit is contained in:
@@ -1031,3 +1031,8 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
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.
|
||||
- **A-416a** (A-416, A-298; principles 1 and 7: one source of who holds a seat, and nothing followed that nobody reads)
|
||||
FollowSeat follows a state of a holder, and the registry seats keep none the builder reads; so the builder knows a
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user