Chapter 2 — Destination and rules first

Status: DRAFT 1 (2026-09-21), DESIGN v6 §4, §9. Sources: docs/artifacts/DELIVERY-SHEET.md; production/phase3/submission-2026-09-14/SUBMISSION-CONFIRMATION.md; ledger rows by line. Ends with the book's one exercise outside the film: the first fenced spend.

2.0 Objective

Given a destination's rules page, you can fill a delivery sheet and a dated cutoff timeline, copy its rights rules into your working agreement, and, given a price at a button, fence and buy one cheapest still and ledger it.

2.1 What you are deciding

Where the film goes, before the story exists. The destination decides the aspect ratio, the frame rate, the loudness, the runtime floor, what may and may not be in the film, where every asset must live, and when it is too late. Our own sheet says why this comes first: these rules "constrain Phases C–G. Discovering these at D5 means regenerating or withdrawing" (DELIVERY-SHEET.md:3–4).

Three documents come out of this chapter: the delivery sheet (every requirement, with the page section it came from, and "silent" written where the page is silent), the cutoff timeline (every dated event, with the date you read it), and the rights lines of your working agreement.

Two rules from Chapter 0's full set land here, because this is where they bite: never attach a real person's likeness or voice to any generation, and, if your destination requires it, nothing generated off-platform enters the project. Ours required both.

2.2 How we did it

The festival's rules, read on 2026-09-04 and written into one sheet (DELIVERY-SHEET.md:20–43). The rows that changed the production:

Row What the page said What it did to us
Runtime "Minimum 3:00, hard" (:26) every cut was measured against 180 s; the lock was 3.3 s over it
Aspect, fps 16:9 or 21:9 allowed; frame rate silent Director chose 16:9, 24 fps; "silence is a Director decision, not a pass" (:16)
Loudness silent Director set −14 LUFS for the social post; the true-peak field on the sheet stayed blank ("peak: ____", :25) and stayed blank to the end
Audio "All audio must be AI-generated"; every file uploaded into the project; tool identifiable on request no music model on the platform, so the score was generated elsewhere and uploaded (Chapter 14)
Likeness "No identifiable real person, likeness or voice, ever — consent does not override" (:29) a clip of a real actress was attached once as a reference; the generated face drifted toward her (LESSONS.md:45, L4: "A real person on screen in any reference leaks identity into the take"); real-cast clips were excluded from the project as references of any kind from then on
Music "licensed, stock, human-composed or recorded music is prohibited", including your own (:30) Chapter 14
Where generation happens inside the one festival project, "Generating on any other AI platform is disqualifying" (:37); external tools allowed "provided they generate no new AI imagery" (:38) the storyboard and animatic were made off-platform and never entered the project (Chapter 10)
Minimal viable submission final video with watermark and packshot and a public social post from a public account; "Missing either = incomplete" (:39) Chapter 15
After the deadline "the entire project becomes public" (:28) every prompt and every failed take is public now

The timeline as recorded, with what it did to us (DESIGN §9):

Event As read What happened
Deadline on the sheet Sep 14 2026 23:59 UTC, read 2026-09-04 (:7) CUT08 submitted Sep 14 evening PDT; platform showed "Project is in review" at 2026-09-15 00:02 UTC; no receipt id (SUBMISSION-CONFIRMATION.md:10–12)
Deadline on the rules page inside the project Sep 16 2026 23:59 UTC, "last updated Sep 16", read 2026-09-16 17:38 PDT (ledger row 596) two more days existed; nobody re-read the page until the director's cut was finished
Director's cut finished 2026-09-16 17:21 PDT; approved 17:32 resubmission asked for at 17:38; contest page read "Contest is finished" at 17:39 (row 598)

Nothing in that table is a rule violation. It is a page that was read once, on day one, and not again on submission day.

2.3 Case 2-A — the page that changed after we read it

Two smaller records worth keeping: the submission produced no numeric receipt, only a status string and a timestamp we took ourselves (SUBMISSION-CONFIRMATION.md:12), so the W7 confirmation rule is "record the platform's state and your timestamp; a receipt if one exists". And the account handle on the sheet (:9) differs from the one in the submission URL (SUBMISSION-CONFIRMATION.md:7); the sheet was not updated when the account changed. Sheets drift; the page is the source.

2.4 Do it with your tools

Destination type What decides the sheet Appendix D checklist
Festival or contest on a platform (ours) the rules page, the project's own settings, the submission wizard's fields D.1
Video platform (YouTube, Vimeo, X) the platform's upload spec (aspect, codec, loudness normalisation); your own rights rules D.2
Your own site your player; you set the rules, and you write them down anyway D.3

If your destination has no rights rules, your sheet still has the rows, filled with your own answers. "No real likeness" is a good rule with no festival behind it.

2.5 Your turn

Time cap: one evening for the sheet and timeline; one hour for the still. Spend: the cheapest image job on your platform, once, priced at the button.

  1. Choose the destination and open its rules page. Fill the delivery sheet (Appendix C.16) row by row with the page's wording and section; write "silent" where it is silent and decide the row yourself, marked as your decision.
  2. Fill the cutoff timeline (C.17) with every dated event, the date you read each, and your own plan date with margin.
  3. Copy the rights rows into the working agreement's "Never" line.
  4. Choose the platform and create the project the destination requires (if it does). If the destination does not choose for you, pick from a current price read, not from ours: Appendix A.5 shows four platforms, two of them Chinese (Kling, Jimeng), with what each public page said on one date, and the only per-second figures any page gave. Read the pages again on your date; the book's process does not depend on which you pick, and every chapter's tool table has an "if yours lacks it" column. Everything generated for the film from now on lives in that project.
  5. The first fenced spend, outside the film. Write a fence (C.3) for one still: any subject, the cheapest image model, one image. Read the price at the button (zoom, screenshot). One click. Verify the job exists. Ledger the queued row with the read price, then the read row with the actual charge from your account. Look at the image. Ledger one sentence of what you see. This still is not for the film; it is so that your first credit is spent under a fence before anything you care about is at stake.
  6. Re-read the rules page and note the "last updated" date, if the page shows one, in the timeline.

2.6 Gate

Each line needs valid evidence per DESIGN §5; outcomes are pass / fail / unverified, and unverified blocks.

Pass example from HALFWAY: the still fence for the final shot (production/phase3/post-submission/final-shot-2026-09-16/final-shot-still-fence.txt): purpose, two platform-only references, "Expected price: 2 credits (read on button before Cmd+Return). One job.", the total against the account balance, and "Director spend approval required before Step 1." Fail example: the deadline row, read once and never again.