Module 11. One finished piece, made with every module in this course, shipped inside a week. Not an exercise. A film that exists, that you can show someone, made by a pipeline you now own.
Sixty to ninety seconds. One character. One location. One idea.
That is not a beginner's version of the real thing. It is the version that gets finished, and a finished ninety seconds beats an abandoned eight minutes in every way that matters, including what you learn.
The most common failure at this point is scope. Two characters doubles your consistency work. Three locations triples your look work. Resist it for this one film.
Because the pipeline runs while you sleep, and a week has seven nights in it.
The parts that take real time are unattended. The parts that take you are measured in hours, not days.
| Day | What you do | What runs overnight |
|---|---|---|
| Mon | Story. Idea to shot list. Module 2 | nothing yet |
| Tue | The bible. Characters, location, look. Module 5 | first stills queue |
| Wed | Choose the frames. Approve or reject. Module 3 | approved frames only |
| Thu | Motion notes on approved shots. Module 4 | the video queue |
| Fri | Watch it all. Fix six shots, not forty. Module 5 | the re-runs |
| Sat | Sound. Spot list, cues, takes. Module 6 | the audio queue |
| Sun | Paper edit, cut, deliver. Modules 7 and 8 | the export queue |
Five of those seven days end with you starting something and leaving.
One first, then the rest. Every queue, every day, no exceptions.
Twenty minutes of watching a queue do two shots on Tuesday saves you the entire Wednesday where forty shots came back wrong in the same way.
You already know this from Module 10. This is the week you find out whether you believe it.
Not "good." Finished means:
That last one is the actual finish line. A film nobody has seen is a project.
It might not be. First films made with a new pipeline often are not.
Ship it anyway, then ask the question that makes the next one better:
"Compare the shots I approved against the shots I rejected. What do the approved prompts have in common that the rejected ones do not?"
A finished bad film teaches you more than an unfinished good one, and it teaches it in writing, into _presets/, where the next film starts.
| Week | The only thing you do |
|---|---|
| One | Change nothing. Make a second film with exactly what you have. |
| Two | Fix the three moments that cost you the most time. Nothing else. |
| Three | Put what you learned into _presets/ and your standing instructions. |
| Four | Test the restore again. Watch a guard fire. Then make a fourth film. |
The system is a byproduct. It is more fun to build than the work is to do, and that trap has eaten more careers here than any technical limitation. If a week produces no film, that week produced nothing, however good the setup got.
Not a tool you learned. A pipeline you built, that runs at night, that gets cheaper every time.
And a film, which is the only part anyone else will ever see.
The tool prepared, organised, drafted, checked, converted, verified and accelerated.
It did not decide what the film was about. It did not choose the take. It did not know when the scene ran long. It has never been moved by anything.
The filmmaker cuts. The tool prepares.
That was true in Module 0 and it is true now, and everything in this course was built to keep it that way.
_presets/. Then start the second film.Module 12 points everything you just built at the one job in film and television that this work is structurally best at, and it is the one people pay for.
The bonus session goes underneath all of it: what the terminal actually is, how to give it a memory, how to run a crew of agents, how to make it refuse things, how to build a studio from nothing. It assumes you know none of it.
You do not need the bonus session to make films. You need it to make the system yours.
The Sizzle. Ninety seconds that make an unmade film feel real, which is the piece that gets one financed.
Verified against Claude Code 2.1.220 · 2026-07-30.