Play Mode, Saves, and Diagnostics · Version 0.5
Validation and Safe Authoring
Understand why Filmstrip refuses unsafe project roots, references, edits, saves, asset operations, migrations, and builds instead of applying partial changes.
Filmstrip treats a refusal as part of the authoring workflow. Project definitions, scene documents, player saves, asset moves, project settings, and builds are validated before they replace accepted state.
Current safety boundaries
- Atomic versioned JSON writes and last-valid-snapshot retention.
- Cross-registry and project-wide reference validation.
- Shared commands with failure rollback and grouped transaction rollback.
- Preview-first destructive object, template, tag, and asset operations.
- Fresh-process project opening and validated project roots.
- Typed missing-reference repair and contained asset movement.
- Complete candidate runtime construction before save load.
- Build preflight before packaging and deterministic content collection.
- User-local recovery, saves, logs, and temporary data separated from project source.
Unsafe loads remain read-only
When a document is malformed, unsupported, or incomplete, Filmstrip keeps the previous accepted in-memory snapshot where possible and refuses writes that could destroy the original evidence.
Actionable paths
Validation messages use document paths, field paths, source IDs, or asset owners so the creator can locate the failed reference instead of receiving only a generic save error.