Expand description
Replication, from the app server’s side.
One Replica per synced workspace, registered with the bridge, driven by announcements
from it and by local edits.
See docs/superpowers/specs/2026-09-16-process-architecture-design.md §4.2.
Re-exports§
pub use id::SYNC_ID_FILE;pub use id::WORKSPACE_MAP_FILE;pub use id::sync_id;pub use id::sync_id_path;
Modules§
- id
- A workspace’s identity across devices.
Structs§
- Backfill
Timing - How the primary device paces its backfill (#188).
- Bridge
Connector - How a
SyncRuntimereaches the bridge, on start and whenever it has lost it (#244). - Peer
Info - What
SyncRuntime::peersanswers with. One device of the workgroup. - Peers
Result - What
SyncRuntime::peersanswers with. Result ofPEERS. - Sync
Runtime - Replication for one application’s workspaces.
- Sync
Status - What
sync.statusreports. - Watcher
- Watches workspace roots and reports which one changed.
Constants§
- DEBOUNCE
- How long events are coalesced before a root is reported.
- DIAL_
BACKOFF_ MAX - The longest the dialer stays away from a peer that keeps refusing.
- OPEN_
TIMEOUT - How long a dial waits for the bridge to open a stream to a peer.
- RECONNECT_
BACKOFF - How long
SyncRuntime::keep_connectedwaits before its first retry after the bridge could not be reached. Each failure doubles it, up toRECONNECT_BACKOFF_MAX. - RECONNECT_
BACKOFF_ MAX - The longest
SyncRuntime::keep_connectedwaits between two attempts to reach the bridge: a bridge that comes up is found within this long.
Functions§
- sync_
router - Add
sync.enable,sync.disable,sync.mapandsync.statustorouter.