Spell out an automation before it touches files

A folder script that renames or moves the wrong files is hard to undo. This automation contract is where you record the decisions, inputs and acceptance checks before the script is written, so the work is easier to repeat and share.

You fill in the input and output folders, included file types, transformation rule, naming rule, collision behavior, repeat-run behavior, the dry-run and apply commands, and a recovery plan.

Worked examples set the expected result for each case: normal input gives the expected output, empty input changes nothing, a duplicate name is an explicit conflict, a symlink is skipped, and an interrupted run leaves originals intact.

You need only a text editor, and you keep the completed plan for your next project. Provider accounts, model weights, GPU compute and hosting are not included.