Collaborate with real-time sync

Understand shared CRDT editing, local episode focus, presence, offline behavior, and reconciliation.

One shared document, independent views

Script and Cinema creative documents synchronize through a conflict-tolerant collaborative document. Keyboard edits and accepted AI edits enter the same shared state. Collaborators can work in different dimensions or episodes without forcing navigation on one another.

Presence shows who is connected and can distinguish synchronized online work from local editing. Presence is awareness, not a lock. Two editors can still change related content, so coordinate broad structural operations.

Temporary disconnection

The workspace has a local persistence layer. A network interruption can leave you editing locally until synchronization returns. Watch the connection indicator and avoid duplicating the project in several tabs as a recovery strategy. When the connection returns, let reconciliation complete before making a second copy of the same change.

Data that is not in the collaborative document

Comments, knowledge files, worldview, advisor relationships, generation tasks, and assets use project APIs and database-backed stores rather than screenplay CRDT nodes. They still respect project membership, but their update and reconciliation behavior differs from text editing.

Safer team habits

• Name a version before a large rewrite or episode deletion.
• Tell collaborators which episode and layer you are changing.
• Normalize shared character and location names before attaching production data.
• Use comments for review rather than encoding discussion in screenplay action.
• Export stable delivery copies when a milestone leaves the workspace.

Synchronization prevents ordinary edit loss; it does not replace editorial communication or intentional checkpoints.