Treat local saves as the default workspace
Most sessions begin as experiments. A local-first setup lets you iterate quickly without committing every draft to the cloud.
It also gives you a cleaner mental model: start locally, export when needed, sync only when the run matters.
Export before big structural edits
If you are about to split branches, rewrite world state, or promote the run into a campaign, export a portable copy first.
That keeps recovery simple and makes device-to-device movement predictable.
- Export before major narrative surgery.
- Sync after stable checkpoints, not after every tiny change.
- Keep your cloud slots for stories you expect to revisit.
Use cloud sync as a continuity tool, not a habit
Cloud sync is strongest when it protects campaigns, active co-creation, or longer story work that may continue on another machine.
Used this way, it feels like a savepoint system rather than background noise.
