Jazz Sync Architecture

This is the all-in-one operating manual for end-to-end Jazz design decisions.

Use it when problems span multiple domains or when you need architectural decisions that remain correct across runtime, schema, sync, branch, and worker boundaries.

System Model

• Jazz state is distributed local-first state, not centralized server-row truth.
• CoValues are collaborative CRDT-backed values with eventual consistency.
• Account/root/profile define graph entry points and permission boundaries.
• Server workers are peers with their own accounts, not privileged bypass channels.

Architecture Domains

1. Runtime and crypto bootstrap (load-edge-wasm, startWorker, Node-API/WASM)
2. Loading and subscription lifecycle (resolve, $isLoaded, loadingState, ensureLoaded, subscribe/unsubscribe)
3. Schema, ownership, and sharing boundaries (co.map/list/record/feed, account/group ownership)
4. Migration and version policy (account vs CoMap timing, additive evolution, mixed versions)