One opened blob, ready to serve ranges. Held by a host that is streaming or
seeking a blob (playback probing a codec header, then a tail, then decoding
forward) rather than loading it whole.
The out-of-band kickoff: the offer plus everything the transport needs to
carry the rest of the exchange. The host encodes this however it delivers a
join code; coven does not choose that encoding.
The complete response when the Store and joining device use the same
provider principal. The one activation commit both publishes the attempt
bootstrap and activates the joining registration, so the joiner can install
that exact history and finish without a second transport wait or catch-up.
The two sides of a join. One device admits — it answers the access
request, prepares the storage grant, signs the approval, registers the
device and activates it — and the other is the device being admitted.
A same-provider registration needs no second signature: the joining
device’s access request already signed the complete registration. A
cross-provider registration additionally signs the response slot allocated
after the administrator publishes its challenge.
The joining device’s current user-visible operation. These values describe
the work actually executing or the exact counterpart artifact being
awaited; hosts render them directly instead of collapsing the whole join
into one indeterminate state.
A joining device’s retained progress sink. Provider reads keep a clone while
their response stream is active, so every received buffer reaches the host.