Built a short film with Agent One (
@invideoOfficial). Here's the honest workflow breakdown.
**The story:** A family goes hiking. Their bulldog Nikita scares off a bear. They find a hidden waterfall — with a cave behind it, and bear cubs inside. Mama bear comes back. A storm rolls in. The morning after.
Four scenes. ~2 minutes 20 seconds.
**Before a single frame rendered:**
Character master sheets for all four — Dad, Mom, Kid, Nikita. Location references for the trail, the waterfall exterior, the cave interior, the storm trail, the shelter, and the forest the next morning. A 9-panel storyboard for every scene. Nothing moved to production until the bibles were locked.
**Then, scene by scene:**
Briefs → generation → review → fix. The word "iterative" doesn't capture it — here's what it actually looked like:
- Mom (Maya) disappeared from frame whenever the bear entered the cave. Six attempts: Seedance V2V, Kling 3.0, Kling Omni reference mode, back to fresh Seedance with a character fidelity template. That last one held.
- A clip came back with two Nikitas. Kling tried to fix it and returned three. Fresh Seedance generation, strict lock, ONE bulldog explicit in the prompt. Fixed.
- A storyboard panel had two kids. One regeneration with the constraint locked hard. Fixed.
- The "run through the storm" clip had Nikita running ahead of the family. Regenerated with her locked to their heels.
Every fix was a production decision, not a retry.
**What Agent One actually did:**
Built and managed the full production board. Wrote the character bibles and location sheets. Dispatched every generation with the right references. Reviewed each clip against the storyboard. Caught the errors before I saw them (and some after I saw them). Ran the fixes. Assembled four scene slates. Stitched the final cut.
I directed. Agent One produced.
youtu.be/kJIJ6DNsgtw?is=Ka7z…
#invideo #animation #aishortfilm #invideocpp #Adventures