Version History

Version History

Overview

The Version History system in ACT 3 AI enables creators to track, branch, and manage changes across their projects. It supports non-destructive editing, collaborative iteration, and rollback functionality—ensuring that every creative decision is preserved and recoverable.

1. Purpose

• Track changes at the script, scene, shot, and asset level
• Allow safe experimentation through branching and merging
• Enable collaborative review with comment threads per version
• Provide visual diff and rollback tools for creative control

2. Versioning Scope

• Projects
• Scripts and Dialogue
• Story Beats and Scene Structure
• Camera and Cinematography Settings
• Character Design and Performance
• Visual Assets (Sets, Lighting, Costumes)
• Render Output Metadata

3. Key Features

• Auto-Save Checkpoints: Save state after major edits or renders
• Manual Snapshots: User-created named versions
• Branch & Merge: Explore alternate storylines, then re-integrate
• Compare View: Side-by-side visual or script diff
• Lock Versions: Prevent changes to approved content
• Restore Point: Roll back to any previous version

4. Collaboration Support

• Comment threads tied to specific versions
• Reviewer tags and approvals
• Version summaries for tracking what changed and why

5. Naming & Metadata

Each version includes:

• Timestamp
• Creator/editor name
• Description of changes
• Affected scenes, characters, or assets

6. Visual Diff Tools

• Shot comparison: keyframe-to-keyframe visual delta
• Dialogue diff: colored text changes with markup
• Lighting or camera path animation previews

7. Access & Permissions

• Editors and Owners can create branches and merge
• Viewers can browse history but not modify
• Roles can restrict overwrite or deletion of locked versions

8. Storage Impact

• Versioned assets consume cloud storage quota
• System prompts to archive or delete older versions if quota is exceeded
• Archived versions remain accessible in read-only mode

9. Export Options

• Export specific versions as:

 * Final Draft (for scripts)
 * FBX/GLB (for scenes or characters)
 * MP4/MOV (for video renders)
 * YAML/JSON (for metadata snapshots)

10. Roadmap

• Timeline-based visual version history
• AI-suggested reverts based on performance analytics
• Version tagging for milestones (e.g., "Festival Cut", "Client Review")
• Multi-user conflict resolution with live merge previews