Re-exports§
pub use store::MemberAdmission;pub use store::AdmittingDeviceJoinProgress;pub use store::DeviceJoinApproval;pub use store::DeviceJoinApprovalPolicy;pub use store::DeviceJoinDriveOutcome;pub use store::DeviceJoinError;pub use store::DeviceJoinJournalDatabase;pub use store::DeviceJoinOfferBundle;pub use store::DeviceJoinTransportError;pub use store::DeviceJoinTransportKind;pub use store::DeviceJoinTransportParams;pub use store::DeviceJoinTransportTiming;pub use store::DeviceProviderAccessAdministrator;pub use store::JoiningDeviceJoinProgress;pub use store::JoiningDeviceJoinProgressObserver;pub use store::BlobCacheError;pub use store::BlobStream;pub use store::EagerCacheFillError;pub use store::EagerCacheFillProgress;pub use store::EagerCacheFillStatus;pub use store::HeldStoreCoordinate;pub use store::HeldStorePosition;pub use store::HeldStorePositionReason;pub use sync_loop::BlockedOperation;pub use sync_loop::BlockedOperationId;pub use sync_loop::RetryStuckReclaimError;pub use sync_loop::SyncLoopFailure;pub use sync_loop::SyncLoopStatus;
Modules§
- cycle
- Sync cycle orchestration.
- store
- sync_
loop - Sync loop handle: runs the background sync loop on a prepared OS thread.
- test_
helpers - test_
owner_ graph
Structs§
- Device
Activity - Activity summary for a single remote device.
- Device
Join Abandonment - Device
Join Activation - Device
Join Journal Record - Device
Join Readiness - 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.
- Sync
Loop Alerts - Sync
Loop Success
Enums§
- Device
Join Action - Device
Join Role - 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.
- Device
Join Status - Derived from a journal record on demand and never stored, so it carries no wire form of its own.
- Device
Provider Admission Completion - Device
Provider Readiness - 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.
- Sync
Error