How sync works
How saved files become causally accepted changes across a trusted fleet.
Immutable content
Files are divided into immutable content-defined chunks. Repeated bytes are reused, so a small edit does not resend the rest of a large file or folder.
Causal ordering
Each node and entry change advances from an accepted parent. A stale compare-and-swap never guesses a winner; it produces a deterministic keep-both conflict entry.
Git metadata
Ordinary worktree files synchronize incrementally. A repository's .git directory also transfers incrementally, but applies only after the complete staged state validates as one recoverable transaction.
Reconciliation
The background service watches stable saves, publishes durable outbox events, applies accepted remote events, and periodically reconciles metadata. Offline work keeps its identity and retries after reconnecting.