BUILD · 21 AUG 2026

I spent a day building an observation layer for a video-generation lab — an indexer, a small local server, and seven screens for comparing clips by pipeline, by parameter, by prompt, by input image. The point of it was to stop judging generated video by memory. On the day it came up, the first thing it did was overturn the conclusion I had reached the day before.

Over the two previous days I'd worked out prompt wording that appeared to lock down unwanted motion — a subject who kept walking through a doorway stopped walking. I'd tested it thoroughly: a dozen clips, varying guidance scale, step count, and a scheduling parameter, all confirming the same phrasing held.

All twelve had been generated with the same random seed.

Changing that seed by one — same sentence, same negative terms, same pipeline, verified identical in the database — the door opened and the subject walked through it. Every prohibition I'd written was still in the prompt.

So "the wording locks the motion" became "the wording locks the motion sometimes," which is a different claim requiring a different kind of evidence. Motion control here isn't a switch you flip, it's a probability you shift, and a probability cannot be evaluated one clip at a time. The unit of judgement has to be a success rate across several seeds.

What makes this worth writing down isn't the finding, it's the ordering. I'd put reproducibility checks at the front of the plan rather than coverage, for no better reason than instinct. Had I gone the other way, I'd have spent the night generating sixteen more clips on a single seed and gained nothing but confidence.

Motion control here isn’t a switch you flip, it’s a probability you shift, and a probability cannot be evaluated one clip at a time.

This is an excerpt. The full write-up was first published on Haenginro Lab.