How to version your AI takes so you can always go back

There is a particular frustration that visits every solo AI filmmaker sooner or later. You generate a take, decide it is not quite right, overwrite it or let it vanish into the model's unnamed output folder, then regenerate. The new take is worse. You try again. By the fifth attempt you cannot remember what the first one looked like, and you have no way of getting back to it. The seed is gone, the prompt has drifted through three small edits, and the credit spend is quietly adding up.

The problem is not the model and it is not your taste. It is that AI generation tools are almost universally built around a single output, not a versioned collection. They return a file, not a project. That framing pushes you toward a linear, destructive workflow: generate, judge, discard. Professional production has always worked the opposite way. Dailies are kept. Takes are numbered. Nothing is thrown away until picture lock. Borrowing that discipline costs nothing in money and very little in time, and it will change how confidently you work.

The core habit: the take folder

Before you generate anything for a scene, create a folder for that scene and number your takes inside it as you go. The structure does not need to be clever.

```
/project-name
/scenes
/sc01_opening-street
/takes
sc01_t01_wide-approach.mp4
sc01_t02_wide-approach.mp4
sc01_t03_tighter-angle.mp4
/selects
sc01_SELECT_t02.mp4
sc01_prompt-log.txt
/sc02_café-interior
...
```

Every file gets a name before it goes into the folder. Your operating system's default naming (output_20260925_143211.mp4) tells you nothing in three weeks. The name `sc03_t04_handheld-push-in.mp4` tells you the scene, the take number, and the shot intent. That is enough.

The selects folder holds only the take you are currently planning to cut. Moving a file there is a deliberate act, not a default. It forces a small decision rather than a passive one.

The prompt log is not optional

Every take folder gets a plain text file that records, at minimum, four things for each take: the take number, the full prompt text used, any settings that differ from your project defaults (aspect ratio, duration, motion intensity, seed if the tool exposes one), and a one-line note on why you moved on or what you liked.

```
sc01_t01
Prompt: "Wide establishing shot, woman walking away from camera down a rain-wet cobblestone street at dusk, shallow depth of field, muted blue-grey tones, slow steady push forward"
Settings: 16:9, 8s, motion: medium
Note: good atmosphere, figure too small, try closer

sc01_t02
Prompt: "Medium-wide establishing shot, woman walking away from camera down a rain-wet cobblestone street at dusk, shallow depth of field, muted blue-grey tones, slow steady push forward"
Settings: 16:9, 8s, motion: medium
Note: SELECTED. Figure readable, motion correct, slight sky flicker at 6s, manageable in grade.
```

This log is what lets you reconstruct a take. If a tool exposes a seed, log it. If it does not, the full prompt plus settings is your best approximation. You will not recover an identical frame, but you will recover the intent, and that is usually what you actually need.

Marking selects without deleting rejects

The instinct when you find a good take is to clear out the others. Resist it, at least until after the scene is cut and you are certain. Disk space for short video clips is cheap compared to the credit cost of regenerating. Keep the rejects in the takes folder and move only the chosen clip to selects. If the edit does not work and you need a different angle or timing, you may find that sc01_t01 is exactly what you need after all.

After picture lock, you can archive or delete the rejects. Not before.

Versioning prompt changes as a separate take series

If you change the prompt substantially, that is a new take series, not a continuation. Append a letter to signal the branch.

```
sc01_t01a_original-approach.mp4
sc01_t01b_original-approach.mp4
sc01_t02a_tighter-angle.mp4
sc01_t02b_tighter-angle-night.mp4
```

The letter suffix tells you at a glance that t02a and t02b share a prompt family, and that the a-series and b-series are genuinely different directions. When you are reviewing twenty clips from a long session, that distinction is the difference between clarity and chaos.

The weekly selects review

At the end of each working session, or at the start of the next one, spend five minutes reviewing your selects folders. Check that every select is named correctly, that its prompt log entry exists, and that you still think it is the right take. This review catches drift early: the moment when you selected something provisional and then forgot it was provisional.

For a multi-scene project, a single running document that lists scene number, select filename, and a one-line status (rough cut, final, needs pickup) gives you a production overview you can scan in thirty seconds. That scan is worth more than any project management tool you might bolt on later.

The next time you generate, name the file before you close the tab, write the prompt into the log before you forget what you changed, and move the keeper into selects before you call the session done. None of this takes more than two minutes. It is the entire difference between a project you can navigate and one you eventually abandon.