Using the production checklist
On this page
This checklist extends the Night Watch action plan and the existing AI Film Workflow checklist into the current studio workflow. It contains 97 checks covering all 31 specialist modules and all 20 decision gates. It is a reusable control set, not a promise that checking boxes produces a good film.
Start each film
- Community edition: save one starter draft in this browser, download its text packet, and use the blank CSV ledger. For separate browser-local projects, revision checks, checklist JSON and full ZIP backups, open My projects at /projects/. Nothing is uploaded or synchronized. Keep production records in your own project folder.
- Declare the actual inventory and boundaries. Add each asset, scene, shot, generation attempt, candidate clip, edit seam, change/repair, cut version, sound cue or scene mix, master, destination and archive package. No sampling: every unit needing a check gets its own record. At early stages some scopes are not yet known; keep inventory unconfirmed and record the missing set.
- Assign named owners and pin current versions. The suggested role is responsibility guidance, not a person's identity. Use current approved canon and applicable destination rules; do not inherit Night Watch's deadline, runtime, team structure, safe band, score or model duration.
- Work stage by stage using the workflow's G00-G19 gates. Each checklist row points to the relevant department modules and expected evidence. The gate register retains decision ownership; a tracker row does not authenticate authorization.
- Update records when an actual state changes. Generated, reviewed, creatively accepted, exported, uploaded and submitted are distinct events. Record paths/IDs, timestamps or timecodes and review coverage; do not paste private account credentials.
What each state means
| State | Meaning | Required next action |
|---|---|---|
| Not started | No work/evidence yet | Assign owner and prerequisites |
| In progress | Work underway; criterion not certified | Finish and review |
| Blocked | Dependency or required decision missing | Name blocker and next owner |
| Failed | Observed result contradicts criterion | Bounded repair and affected recheck |
| Unverified | Evidence or required modality unavailable | Obtain evidence; never infer pass |
| Verified | This exact unit/version meets the stated check | Retain reviewer, date and evidence |
| Not applicable | A conditional check does not apply here | Record why and responsible owner |
| Stale | Input/version changed since verification | Recheck relevant criterion on new version |
A checkbox is only a visual summary of a verified record. The HTML requires a named owner and evidence before verification; it requires an owner and reason for permitted exclusions. It records the current unit revision and date. These fields improve tracking but do not validate the truth of the evidence or replace independent review.
Repeat checks at the right granularity
| Scope | A separate tracking unit means |
|---|---|
| Project | Whole-film mandate, inventory, story/canon and deadline decisions |
| Asset | One reference, character/location/prop/audio asset and revision |
| Scene | One scene packet and its shared timed beat plan |
| Shot | One planned shot with prompt/reference/edit requirements |
| Attempt | One actual logical generation, including uncertain job reconciliation |
| Clip | One candidate output and selected review interval |
| Seam | One actual cut boundary, including repaired joins |
| Change | One repair or material change and its impact set |
| Checkpoint | One scheduled or triggered time/cost/critical-path decision; preserve each prior decision |
| Cut | One assembled edit/picture-lock version |
| Sound | One cue, dialogue passage or scene mix; document the chosen coverage boundary |
| Master | One actual exported file/version/crop |
| Destination | One upload/publication/submission/handover target |
| Archive | One archive package and restore/relink test scope |
Do not mark all scenes done because one passed. A rough-cut checklist cannot stand in for the exported master. Add replacement candidates as separate clip units. Update versions when relevant inputs change; the HTML marks previously verified checks stale for that unit. Cross-unit dependencies still require the producer's impact list and explicit invalidation of affected units; this tracker does not infer the dependency graph.
A check identity is its check ID plus unit ID and relevant revision. Record parent IDs and exact input/range/join context: scene to shot to attempt/output, and cut to ordered joins to master/destination. Update that context when selected in/out points, neighbours, mix or delivery requirements change, even if original bytes do not. The HTML invalidates verified rows for a changed unit; the producer must still update affected dependent units. Preserve failed/cancelled jobs and rejected unused clips with an explicit disposition and reason; they do not need to pass the current release's creative checks.
At every handoff, compare expected inventory with recorded units, then inspect failed/blocked/unverified/stale items and every required gate. The tracker reports counts, not an automatic release verdict. An inventory confirmation means the producer has reconciled the declared scope for the current review, not that a system independently discovered all media. A single pending required criterion keeps that criterion open regardless of overall percentage.
Every-session rhythm
Community edition: save one starter draft in this browser, download its text packet, and use the blank CSV ledger. For separate browser-local projects, revision checks, checklist JSON and full ZIP backups, open My projects at /projects/. Nothing is uploaded or synchronized. Keep production records in your own project folder.
Save, share and recover
Typing retains a draft; Save check applies the selected status after validation. Draft fields survive saving another row, changing filters and reloading when browser storage is available. Editing a verified or not-applicable record makes its previous verdict stale. Save changed unit context before verifying its checks. A saved draft is not an applied verification.
Keep one editable tab per browser. If another tab changes the saved projects, the older tab pauses saving to protect the newer data. Export its local changes before reloading; imports create separate project copies rather than silently merging decisions. Browsers without the safe storage-lock capability use export-only mode, and storage errors remain visible. Always export at handoff and before moving the HTML to another location; browser storage belongs to that browser and origin.
Community edition: save one starter draft in this browser, download its text packet, and use the blank CSV ledger. For separate browser-local projects, revision checks, checklist JSON and full ZIP backups, open My projects at /projects/. Nothing is uploaded or synchronized. Keep production records in your own project folder.
What changed from Night Watch
The three preserved HTML checklists are historical snapshots. The later conversation and revised-master records show Night Watch was completed and submitted; pending scene boxes in older copies do not overturn that outcome. The enhanced checklist retains scene order, controlled references, signature shots, sound continuity, fallbacks and delivery checks. It adds evidence/version/owner tracking, repeated-unit inventory, full department coverage, bounded retries, actual-composer readback, boundary sweeps and distinct publication/submission/archive checks.
Independent review also clarified conditional checks for non-character/stylized shots, terminal failed jobs without output, separate source handles versus final runtime, repeated deadline checkpoints and local/private delivery without a festival submission.
The old fixed model durations, central safe band, continuous cello and competition runtime are project-specific. The old suggestion to stretch a falling key is replaced by physical timing and coherent coverage. A style-compliance tick is not evidence that the full prompt and reference chips reached the composer. Recovered later submission evidence is kept separate from present-day live platform state.
Review before packaging
This HTML/PDF edition is for the user's and AIC team's review. The existing local skill draft remains uninstalled. Skill finalization and the requested private GitHub project follow explicit user approval of this edition; public release would be a separate later decision. The exact Divinium rubric remains unidentified, so the working rubric is explicitly provisional.