Appendix D — Delivery checklists by destination type

Status: DRAFT 1 (2026-09-21), DESIGN v6 §12. D.1 is filled from HALFWAY's delivery sheet and submission record (docs/artifacts/DELIVERY-SHEET.md; production/phase3/submission-2026-09-14/SUBMISSION-CONFIRMATION.md, DELIVERY-CUT08.md). D.2 and D.3 are the same rows with the platform-specific values left for the learner to fetch; nothing in them is a number we read.

Every row needs evidence per DESIGN §5. A row the destination is silent on is filled by you and marked "my decision".

D.1 Festival or contest run on a generation platform (our case)

# Row Ours, as recorded Evidence you attach
1 Rules page URL, read date, "last updated" read 2026-09-04; the in-project page read 2026-09-16 said "last updated Sep 16" the timeline
2 Container and codec "MP4 or MOV. Codec not specified" (:20) ffprobe of the file
3 Resolution, aspect, frame rate up to 4K; 16:9 (Director); 24 fps (Director, page silent) ffprobe
4 Runtime floor and ceiling minimum 3:00 hard; recommended max 5:00 (:26) verification.json duration; the margin
5 Loudness and true peak −14 LUFS integrated (Director); true peak never set (:25) media.sh loudness --target … --peak … output
6 Watermark and tail card "Official watermark and packshot mandatory" on the film and the post (:28) frame at the tail; frame count including it
7 Subtitles any language with English subtitles; burned in the cue windows measured after the last trim
8 Audio provenance "All audio must be AI-generated"; every audio file uploaded into the project; tool identifiable (:24) the project's asset list with each file; the ledger's tool column
9 Image provenance every generation inside the one project; "Generating on any other AI platform is disqualifying" (:37); external tools only if they "generate no new AI imagery" (:38) the project's generation history; the storyboard's "never enters the project" note
10 Likeness "No identifiable real person, likeness or voice, ever" (:29) the working agreement's Never line; the fences' reference lists
11 Music licensed, stock, human-composed or recorded music prohibited (:30) the score's tool and prompts in the ledger
12 Minimal viable submission the file + a public social post from a public account, viewable without login (:39) the post URL; a logged-out view
13 Public after deadline "the entire project becomes public" (:28) nothing to attach; know it
14 Submission mechanism a wizard: Details / Film / Social post / Go live (row 327); the final button is a binding entry, the Director's click the confirmation record
15 Confirmation state control reads "Update"; menu "Your submission"; status "Project is in review"; no receipt id; our timestamp 2026-09-15T00:02:56 UTC SUBMISSION-CONFIRMATION.md
16 Replacement window pre-deadline swap allowed "no limit" (web page, recorded from a fetch, not archived); nothing after the timeline; the page re-read on submission day
17 Rules page re-read on submission day not done; the deadline had moved two days and nobody saw it until after the timeline's last row
18 Retention sources retained 24 months (:24) the project itself; the local disk

D.2 Video platform (YouTube, Vimeo, X, or similar)

# Row Fetch from the platform's upload spec, with date
1 Spec page URL, read date
2 Container, codec, bitrate ceiling
3 Resolution, aspect, frame rate
4 Runtime ceiling, file size ceiling
5 Loudness normalisation the platform applies (so you know what your −14 becomes)
6 Subtitle file format accepted, or burned in
7 Your own rights rules (likeness, music), written even though the platform does not ask
8 AI disclosure field, if the platform has one
9 Visibility and the logged-out check
10 Confirmation state: the URL, the processing status, your timestamp

D.3 Your own site

# Row You decide; write it down anyway
1 Player and its codec support
2 Resolution ladder, if any
3 Loudness target you choose
4 Subtitles: track or burned in
5 Your rights rules
6 Provenance page: tools and prompts, if you publish them
7 Confirmation: the URL live, checked from a phone off your network, timestamp

D.4 The three lines that apply everywhere

  1. Read the page on day one and again on the day you deliver.
  2. Record the platform's state and your own timestamp; a receipt if one exists; never a status you inferred.
  3. Play the delivered file from the destination, start to end, yourself.