Flywheel: Cedwyn documentary — sequential scene production
Parent: Snowball protocol · Full scene workflow (Markdown)
HubSpot: WP3 master screenplay · WP4 scene production
Documentary: Master screenplay and source ledger · Film and releases
Core rule: nominal two-minute scenes are produced in the approved master sequence, one at a time. Every factual beat needs source IDs, exact locations, contrary evidence and an approved scene pack. Existing F001–F010 material is preserved pending audit.
Every scene requires
- Master-script beat and continuity context.
- Evidence map with sources, page/line/folio/timecode, scope, confidence and counter-evidence.
- Screenplay, storyboard, shot list, set/props/wardrobe and period design.
- Cast/voice permissions, blocking/choreography, camera, lighting, sound, music and edit.
- Model/tool version, prompts, output provenance, subtitles and rights.
- Independent factual, historical, privacy, rights, creative and continuity review.
Semantic versioning
| Version | Meaning |
|---|---|
| MAJOR | Narrative or structural reset. |
| MINOR | Added or materially revised scene/sequence, including new disclosure. |
| PATCH | Correction, grade, mix, subtitle or continuity refinement. |
Preserve prior cuts. A new disclosure triggers scene impact review and possible recreation; never silently overwrite an earlier release.
OmniHuman and other model gate
Verify official or licensed access, model identity, capabilities, API, commercial rights, likeness/voice consent, data handling, cost per accepted scene and cancellation terms. An independent wrapper is not presumed to be official ByteDance. No paid plan or production spend before quote, cap and approval in the procurement register.
Raw Markdown: movie.md · register: flywheels.json · changelog: CHANGELOG.