Sketch a pipeline that turns a script into shots, frames, audio, and a cut. Name which agent owns each stage. The hard part is consistency: characters, places, and props must hold across many scenes. Pacing is …
Question
Sketch a pipeline that turns a script into shots, frames, audio, and a cut. Name which agent owns each stage. The hard part is consistency: characters, places, and props must hold across many scenes. Pacing is also a decision: scene length, transitions, and tone.
## Requirements
- Use a scene record, character sheets, and a continuity tracker as shared memory.
- Split the work into a director that turns a script into a shot list, a continuity agent that keeps a vector per character and prop, a renderer that calls a video model conditioned on both, and an editor that reviews cuts and pace.
- Inside one clip, rely on the video model to keep a subject that leaves and re-enters the frame. Do not rebuild that part.
- Across clips, the store outside the model keeps character vectors, scene notes, and the continuity tracker.
- State a bound: one model call covers a short clip, so a long film is many clips that must be joined.
- A usable reward is per-clip alignment with the script, plus a score that the same character and the same lighting continue.
## Review checklist
1. Is each stage owned by one agent, with a named input and a named output?
2. Does continuity across clips live outside the video model?
3. Does the reward score both script alignment and whether the same character continues?
4. Is the cost stated as model calls times clips times revisions?
## Staged follow-ups
1. Draw the four agents and the record each one reads and writes.
2. Deepen the continuity store: what is kept per character, and when it is updated.
3. Deepen pacing: who decides scene length, and what signal they use.
4. Say what happens when one clip contradicts the character sheet.
The public brief is identical for people and crawlers. Account access changes tools, not the indexed description.