Production context

Canonical ground truth for how FFILM.org titles move through the pipeline and how crew credits are ordered. Linked from the Developer recruitment hub for assistants (including Claude) that need the same facts humans see.

Machine-readable twin: structured data lives in development-data.json (same directory). The Developer page loads it to assemble prompts. If this page and the JSON disagree, treat this page as the copy humans proofread — then update the JSON.

Crew credits: first come, first served (per department)

Credit blocks are ordered chronologically within each department lane (writers, camera, sound, post, production, art/costume, VFX, music, other). Someone who commits early in sound sits higher in the sound block than a sound colleague who joins later — but that does not skip them ahead of camera, writers, or any other lane.

Production queue (in order)

Everyone fits somewhere on this rail. Early stages favour story and producing; middle stages favour set disciplines; later stages favour editorial, sound, grade, and delivery.

  1. Stage 1 Discovery & brief Intent, audience, tone, and constraints — what we're making and why. Producers, directors (early), writers doing research, community liaison.
  2. Stage 2 Development Bible, beat sheets, drafts — story and world before greenlight. Lead writer / room, IP continuity, early storyboards.
  3. Stage 3 Pre-production Schedule, budget, locations, casting, shot design, tech scout. Line producer, 1st AD, locations, casting, DP, gaffer, sound prep, art, costume.
  4. Stage 4 Production Principal capture. Director, camera dept, sound, script supervisor, grip/electric, art, stills/BTS.
  5. Stage 5 Post-production Picture cut, sound, grade, VFX, music. Editor, AE, colourist, mix, composer.
  6. Stage 6 Delivery & launch Captions, accessibility, platform masters, premiere, archive. Post supervisor, online, distro, marketing.

Using this with Claude (or any assistant)

Paste the URL https://ffilm.org/development (or this page) into the conversation, or use the Developer hub to copy a single prompt bundle that already embeds the JSON context. Instruct the model to:

Recruitment handoff

After someone self-serves here, they should still introduce themselves on the project thread or via Contact so a human can timestamp their lane. The assistant is for orientation, not a contract.

Open recruitment hub