Compare two creative briefs without losing the original
A version should explain a decision. Keep the old wording, name what you changed and compare the actual fields before you use a new brief. Local storage is convenient, but your downloaded backup is the copy you control outside this browser.
Written and documentation checked
1. Save a baseline before a revision
Start with “The held portrait”. Build its brief, review both subjects and save a version called “01 — fixed camera”. Then change only the camera to a gentle push-in, rebuild explicitly and name the next version “02 — slow approach”. These names describe the experiment; they do not claim a better video.
The compare panel shows differences in title, structured settings, shot plan and editable text. It does not run a model, judge artistic quality or infer why a later output changed. Keep other variables recorded so a future test can be interpreted carefully.
2. Know which file preserves what
| Export | Contains | Use it for |
|---|---|---|
| Project JSON | Current fields, shots, checks and exact editable brief. | Reopen this workspace. |
| Library backup | All saved projects and their named versions. | Backup before clearing local storage. |
| Classic draft JSON | Basic settings and editable text; no new shot-editor structure. | Use the older helper. |
| TXT / print to PDF | Readable brief and empty fields for a future real test record. | Review or hand off after checking private notes. |
3. Import without silently replacing stored work
The workbench reads current project JSON and older schema-2 DuoFrame draft exports. Older drafts retain their exact text and subject settings; they become one planned shot because the old format did not store a multi-shot editor. Review the new shot settings before rebuilding.
Import replaces only the current workspace and offers Undo. It becomes a stored project only when you choose Save. A whole-library restore is different: it requires confirmation and replaces that library. Export first if you need both sets.
4. Keep a portable and private handoff
The local library holds up to eight projects with five named versions per project. It does not silently remove old entries. If the limit or browser quota is reached, export a backup and remove something deliberately. Corrupt or unavailable storage does not stop editing or downloading the current project.
Photos are never in these files. Your words can still be private: inspect reference notes, subject descriptions and source locations before sharing. The setup link is intentionally narrower; it carries only workflow, camera and frame, never the brief or storyboard.
Make this decision in a real plan
Read the complete example Load it in the workbenchSources and limits
Provider documentation supports the input distinctions. Practical checklists and example revisions here are original preparation advice. No real render, user study, success rate or cost result is claimed.