Module 9. Every generation you have ever made, findable. This is the module nobody else teaches, it is the reason the last eight modules compound instead of evaporating, and it is the difference between doing this for a month and doing it for a career.
You know what is in there.
kling_20260803_0417_v2_final.mp4
kling_20260803_0417_v2_final (1).mp4
Untitled_video_9.mp4
final_FINAL_use-this-one.mp4
download (47).mp4Forty of those are excellent. You could not tell anyone which forty, or what prompt made any of them, and neither could you in six weeks.
Not the files. The files are fine.
You lost the connection between the file and the thing that made it.
Every module in this course wrote to a log while it worked. Not as bookkeeping for its own sake:
A generation with its prompt, model, seed and settings attached is an asset. The same file without them is a souvenir.
video/log.jsonl, audio/log.jsonl, the bible, shots.json. Those files are your library. The media is just the part that takes up space.
A name should say what the thing is without being opened, and sort correctly on its own.
| This | Not this |
|---|---|
elena-doorway_s014_v03.mp4 | final_v2_USE-THIS.mp4 |
2026-08-17_apartment-wide_s003_v01.png | download (47).png |
Date first if the project is ongoing, shot id always, version always, never a word like final.
"Write my naming convention to NAMING.md as rules, with three examples of a correct name and three of a wrong one. Then check my existing files against it and list every violation. Do not rename anything yet."This is the moment the log pays for every minute you spent on it:
"Cross-reference every file ingenerations/againstvideo/log.jsonl. Rename each one to the convention inNAMING.md. Anything you cannot match to a log entry, move togenerations/_unmatched/and list it. Write the old name into the log so nothing is lost."
Nothing is deleted, nothing unmatched is guessed at, and the old name survives.
Run it on twenty files first. Look at the twenty. Then run the rest.
"Find every generation whose prompt mentions a doorway and warm light, from any project. Give me the file paths, the dates, and the prompts."
That works because the prompt is in the log. It is not looking at the picture.
It cannot see your footage. Every search in this module runs on the words you wrote, the settings you used and the metadata of the file. That is the honest boundary, and it is also exactly why writing good prompts into a log is worth doing.
Since it cannot look, you look, but fast:
"Build a contact sheet of every approved take across all projects, newest first, with the shot id and the first eight words of its prompt under each frame. One page per twenty."
Your eye scans a hundred frames in ten seconds. That is the correct division of labour: it does the fetching and the labelling, your eye does the recognising.
Studio/
_bible/ characters and looks that recur across films
_presets/ prompt fragments that reliably work
NAMING.md
projects/
the-apartment/ shots.json, bible/, video/, audio/, edit/, deliverables/
untitled-doc/
generations/ everything, named, logged, searchable_bible/ and _presets/ at the top are the compounding. Film two starts from a folder that already knows your look, not from an empty prompt box.
"Across every project, find the prompt fragments that appear in shots I approved but rarely in shots I rejected. Draft me _presets/what-works.md from them, grouped by what they control: lens, light, grade, motion. Mark anything you are unsure about."
That is your own style, extracted from your own evidence rather than from a prompt guide written by a stranger.
Storage fills. The instinct is a cleanup, and the cleanup is where films die.
"Report on disk: total size by project, by type, and by month. Show me proxies and superseded takes separately from approved takes and originals. Recommend what could go. Delete nothing."
Never let anything delete media on its own initiative, however confident it sounds about what is a duplicate.
Proxies are regenerable. Originals are not. Anything that cannot be remade from the log is permanent, and it is the one category no automated tidy should ever be pointed at.
Once a month, or after every project:
"Update LIBRARY.md: one line per project with its dates, shot count, models used, where the deliverables went, and one line on what worked. Newest first. Do not rewrite the older entries."
One page, and you can read six months of your own work in a minute. Including the part you would otherwise forget, which is what you learned.
This one is on your real archive, not on the practice film. Set aside an hour.
NAMING.md with rules and examples, then list every file that violates it. Renamenothing."*
_unmatched/. Keep the old names in the log."_presets/what-works.md from the prompts behind my approved shots."_archive/, do not delete."LIBRARY.md, one line per project, newest first."_bible/ and _presets/ so the next film starts ahead of this oneLIBRARY.md, six months of your work on one pageThe work you did in Modules 0 to 8 is now an asset instead of an afternoon.
When It Lies To You. The failures that cost real days, what each one looked like at the time, and the habit that catches all of them.
Verified against Claude Code 2.1.220 · 2026-07-30.