# Flywheel: Cedwyn documentary — evidence-led sequential scene production

**Parent programme:** [Cedwyn Snowball master protocol](snowball.md)  
**HubSpot screenplay task:** [WP3 — documentary bible and master screenplay](https://app.hubspot.com/tasks/149419802/view/all/task/536861939937)  
**HubSpot scene task:** [WP4 — two-minute scene production and model verification](https://app.hubspot.com/tasks/149419802/view/all/task/536712479991)  
**Documentary entry:** [Master screenplay and source ledger](https://cedwyn.bucklerfamily.estate/documentary/script/)  
**Project portfolio:** [Projects / Snowball](https://cedwyn.bucklerfamily.estate/projects/#cedwyn-snowball)

## Purpose

Retell the whole documented story of Great House Farm / Tŷ Mawr and the Williams–Buckler family: Welsh place and estate context, the family and matriarchy, women’s property and agency, landholding and interests, farming and community, architecture, archaeology, quarrying, institutional decisions, court proceedings, eviction and demolition, later records recovery and the proposed Patagonia heritage project.

The film is a source-led documentary, not merely a litigation argument. Inconvenient records, contradictory material, institutional explanations and evidence that weakens a theory remain in the research and script ledger.

## Production rule

Produce sequential nominal two-minute scenes, **one at a time**, in the approved master-script order. Do not independently pick the next scene from whichever prompt is easiest. Do not move ahead until the previous scene's source map, creative brief and quality checks are recorded.

## Required inputs for each scene

- Approved master-script beat and preceding/following continuity.
- Source/evidence identifiers and exact archive or record locations for every factual claim.
- Contrary evidence, uncertainty, alternative explanations and any missing records.
- Character, voice, cast and likeness reference with consent/rights status.
- Location, period, set, props, wardrobe and art-direction brief.
- Storyboard, shot list, camera/lens/movement, lighting, sound, music and edit plan.
- Model/tool name and version, prompts, source assets, generation settings and output provenance.

## Scene pack and outputs

1. Scene number, title, target runtime and narrative purpose.
2. Screenplay with dialogue, action, staging and sound directions.
3. Evidence dependency map: source IDs, page/line/folio/timecode, scope, confidence and contrary evidence.
4. Storyboard and shot-by-shot direction.
5. Set/prop/wardrobe/period design and continuity bible.
6. Blocking/choreography, camera, lens, movement, lighting, sound and music notes.
7. Cast/voice/likeness consent and rights register.
8. Rendered scene, Welsh/English/Spanish language/subtitle assets where approved, edit notes and QA sign-off.
9. Scene-specific changelog, model/tool version, prompts and release-version relationship.

## Existing material to preserve and audit

The documentary storage repository already contains scene script records **F001–F010**, with Welsh, English and Spanish subtitle files. The public film page describes a 148-scene plan. Audit these against the full chronology and evidence ledger before replacing, reordering or recreating anything. Preserve existing scripts, prompts, outputs and earlier cuts. The master script may change the total scene count or sequence, but that change requires a versioned decision and impact review.

## Semantic version policy

| Version | Meaning | Examples |
|---|---|---|
| MAJOR | Narrative or structural reset | Reordered acts, changed central framing, redesigned continuity |
| MINOR | New or materially revised scene/sequence | New disclosure, added scene, substantial factual or creative reconstruction |
| PATCH | Correction or production refinement | Subtitle, mix, grade, edit, factual correction or continuity fix without structural change |

Keep every released cut. A new disclosure triggers an impact analysis of the relevant script beats, scenes, subtitles, graphics and promotional material. Recreate or re-release only where the disclosure materially changes what an accurate and fair telling requires. Mark old versions as superseded; do not silently delete or overwrite them.

## Model access and spending gate

Before any use or purchase of ByteDance/BytePlus OmniHuman 2.0 or another generative-video service, verify the official or licensed access route; model identity; availability; multi-person, motion and duration capabilities; output resolution; API/batch access; commercial-use rights; voice/likeness and archive consent; data handling; retention; cost per accepted scene; and cancellation terms. An independent wrapper is not presumed to be an official ByteDance service. Compare alternatives and enter quote/cost/caps in the [procurement register](https://cedwyn.bucklerfamily.estate/projects/procurement/) and HubSpot WP8 before any commitment.

## Quality gates

- **Evidence:** every factual beat traceable; source and scope checked; contrary evidence included.
- **History:** chronology, names, identities, geography, parcel boundaries and period details checked.
- **Law and privacy:** no unsupported allegations, private correspondence or personal data published; legal wording independently reviewed where material.
- **Creative:** screenplay, performance, staging, choreography, design, camera, sound and pace reviewed.
- **Rights:** archive, image, music, voice, cast and likeness permissions verified.
- **Continuity:** characters, locations, costumes, props, lighting, season, chronology and prior scenes aligned.
- **Release:** accessible captions/subtitles; version, model and provenance recorded; approved master and prior release retained.

## Reporting

Update the same HubSpot task with the claimed scene, status, source IDs, output/version, Git commit/storage reference, reviewer, unresolved issues and next dependency. Report a door as released only after all gates pass and the actual public page/clip is checked. A generated clip is not a completed scene merely because the model returned a file.

Built to the [flywheel schema](SCHEMA.md).