Drives and replication
Authorized discovery and sparse reads, with explicit writer ownership.
Writer and receiver roles
A local Locus or Lens is backed by a signed Strand. A writer owns its key; a receiver opens a remote resource by the source public key. Resource names alone do not confer shared authority.
start_auto_replication() starts listeners, reinstalls sparse session clients and announces known local Strands. It does not discover and copy every peer's data. Sparse reads fetch required blocks through an authorized provider path. Writer delegation remains attached to announcements.
Lifecycle
- Create/open the intended local resource and retain its persistent identity.
- Configure reachable bootstrap and replication transport using
NetworkConfig. - Start networking and announce resources you are authorized to serve.
- Open a remote Strand/Lens/Locus with the correct source public key on the receiver.
- Read through the SDK; handle discovery, authorization, transport and verification errors separately.
- Verify actual returned data before reporting synchronization success.
Actual entry points
See node signatures for start_network, start_auto_replication, announce_strand, open_remote_lens, open_remote_locus, read_block and stop behavior. Replication interfaces document access proofs and session state.
The SDK does not export the old DriveManager/DriveAcl source files as public modules. Use the current node and replication boundaries. Two independent writers do not become one writer by choosing the same store name.
