Structs§
- Cross
Principal Device Registration Request Body - Device
Join Abandonment - Device
Join Abandonment Body - The wire body of an owner’s abandonment of a join attempt.
- Device
Join Activation - Device
Join Bootstrap Closure - The exact verified history required after the selected snapshot. This is a transfer representation; the joining database reconstructs its verified bootstrap plan before mutating any Store state.
- Device
Join Bootstrap Commit Closure - The canonical evidence for one Merge commit required to install a device join. Every value is re-verified against its exact reference before the joining database accepts it.
- Device
Join Offer Body - The wire body of a device-join offer. Every field here is signed.
- Device
Join Readiness - Device
Provider Access Request Body - The wire body of a joining device’s provider-access request.
- Device
Provider Admission Approval Body - The wire body of a provider administrator’s admission approval.
- Joined
Store - Provider
Ready Device Bootstrap - Provisional
Device Bootstrap - Same
Principal Device Join - 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.
- Same
Principal Store Installation - The signed snapshot authority and exact Merge closure a same-provider joining device needs. The snapshot image remains in provider storage and is the only Store object downloaded after this response arrives.
Enums§
- Device
Join Exchange Error - A signed join-exchange value that contradicts itself, its signer, or the exchange it extends. Workflow errors wrap it at the operation boundary.
- Device
Provider Admission - Device
Provider Admission Completion - Device
Provider Challenge Publication - Device
Provider Readiness - Device
Provider Response Reservation - Device
Registration Request - 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.