# Carrying the character into a series The sheet is made once. Everything after it attaches two things: the sheet as a reference and the lock text in the prompt. ## What every later shot takes 1. **The reference:** `character.reference`, the text-free sheet. Attach it first. The labelled `character-sheet.jpg` is for people; models copy its labels. 2. **The lock text:** `character.lock_text`, pasted unchanged. In a prompt with little room use `lock_text_short`. 3. **A reminder line:** "The person is exactly the character on the reference sheet. Use the sheet only for the person; do not copy its backdrop, layout or poses." More than three references dilutes each one, so a keyframe that also needs a location and a product carries the sheet, the location and nothing else, with the product in words. ## Faces and video models Seedance on fal refuses a start frame with a clearly visible realistic face, even a synthetic one (seen in the Cinematic brand film and Destination teaser tests). So: - A **photoreal or stylised 3D** character (both refused in the sample run) is animated with Kling 3 Turbo Pro (`fal-ai/kling-video/v3/turbo/pro/image-to-video`, about $0.14 a second) or Veo 3.1 wherever the face shows. The look of those shots differs a little from the Seedance shots. Say so to the user before the first clip. - Shots from behind, in silhouette or with the person small in frame can still use Seedance. - A **stylised 3D** face was refused by Seedance 2.0 mini in the sample run (fal: "may contain likenesses of real people"), so plan Kling for it too. A **clay** face is untested: the sheet's optional probe (one Seedance 2.0 mini 480p clip, about $0.36, counted even when refused) tests it. - The test clip in this Skill (`--stage clip`) shows the face holding in motion before any series is shot. It is not a deliverable of the series. ## In a film plan `scripts/handoff.mjs --character character.json --film film.json --out film.with-character.json` writes a new plan and never edits yours: - **`meleon-film/1`** (the shared plan read by film assembly): the character goes under `plan.characters`, an array with one entry per character: `name`, `look`, `lock_text`, `lock_text_short`, `never`, `reference` (a path relative to the plan), `face_route` and `people`. The server stores `plan` and never reads it; the Skills do. Shots are untouched. - **`cinematic-brand-film/1`:** sets `locks.cast` and `locks.wardrobe`, sets `references.cast_bible` to the sheet and copies any consent quote. - **`destination-teaser/1`:** sets `locks.people` to the short lock. Each keyframe in the plan names its character, carries `reference`, and starts its prompt with the lock text. ## Checking, before video money is spent Open every keyframe next to the sheet and check: the face, the hair and how it is worn, the outfit, every `never` item. A keyframe that fails is re-rolled; a video made from it will not be better. A clip is checked frame by frame, because a face drifts inside a clip as well as between stills. ## More than one character One sheet per character. Two characters in one frame hold less well than one: where the story allows, cut between singles. Each character keeps its own `character.json`; a plan lists both under `plan.characters`. ## Real people, privacy and retiring a character - A character from a photo carries `consent_quote` and `consent_recorded`. Every Skill that takes `character.json` reads `people` and refuses `real-with-consent` without them. - Delete the user's photo, and any sheet made from it, from the working folders when the series is done unless they want them kept. fal keeps request inputs and outputs on its side for a period: tell the user they can delete them from their fal dashboard, and to check fal's current retention policy. - To retire a character, delete its folder. Nothing else holds a copy.