Offline-First Sync

A peer can dispatch changes while disconnected because the local Chronicle remains usable. When a connection is established, ConsensusCore maintains an Automerge sync state per peer and exchanges sync messages through the configured network connection. Remote changes are applied to the Chronicle, which emits the same state-change events used by local changes.

The network transports CRDT sync blobs, not game commands. A relay can therefore forward messages without storing the game model. WebSocket peer connections are available, and HybridPeerManager can use WebRTC with a WebSocket signaling or fallback path.

Offline operation does not resolve gameplay policy. If two peers make incompatible legal-looking moves while disconnected, Automerge can converge their document representation, but the game must define whether that result is acceptable. Disconnect all peers before compaction and coordinate the same epoch boundary; an offline peer with pre-epoch history cannot safely be treated as current until it has been reconciled.