Offline sync under the hood

This article is for the curious and for troubleshooting.

What gets synced

For each selected production, the sync pulls a bundle containing:

• The production itself and its layers.
• Every template referenced by those layers.
• Every dataset referenced, plus its schema and fields.
• The output the production points at.
• Project fonts that the templates actually use.
• Media assets referenced from templates or datasets.
• The operator's user record (minus password; offline auth uses the token).
• The operator's membership of the production's organization.

Everything in the bundle is scoped to what this specific production needs — no cross-project data leaks into the laptop.

What does not get synced

• Data from other productions or other organizations.
• Plugin credentials (irrelevant offline).
• Session history or audit logs.
• Passwords (there is no "offline password" — auth is via the sync token only).

Integrity

Starting in this version, bundles are signed with HMAC-SHA256. The laptop app verifies the signature before importing, so a tampered bundle is rejected.

One-way

There is no push-back. Any edit on the laptop stays local. For live-edit scenarios where the show value matters, note it down and apply it back on the cloud side after the show.