A Founding Rule, Restated Twice
The workshop's first project established a rule about handmade work: the Nth entry in the roster costs one line of data plus a re-render. The video is derived from data, not handcrafted frame by frame. Add a subject, add a line, rebuild.
When the series arrived, the same rule was moved one axis over: the Nth episode costs one identifier. Not a new directory, not a copied script, not a fork of the pipeline with small edits. One pointer, and the format does the rest.
Both statements are really about the same quantity — the marginal cost of the next instance — and holding that quantity near zero is what separates a tool from a pile of similar work.
Why an Episode May Not Have a Directory
There is an explicit prohibition attached: an episode never creates a project directory. It sounds like housekeeping and it is structural.
Give each episode its own directory and, within about three episodes, each one has a slightly edited copy of the format. Episode two needed a different opening, so its copy diverges. Episode three borrowed from two rather than from the original. Now there is no format — there are N variations with a shared ancestor, a fix has to be applied N times, and the pipeline has quietly degraded into a template that people copy. This happens without anyone deciding it, which is exactly why it is forbidden by rule rather than discouraged by preference.
The Real Test Is Whether Improvements Flow Backward
Here is the property that makes low marginal cost worth the discipline. When the pilot run found problems, twelve of its lessons were fixed in the tool rather than in that episode's data — a geometry check, a cache correction, a measurement that had never been taken per language. Because there is one pipeline, every one of those fixes applies to every future episode automatically.
In the copied-directory world, those same twelve fixes would have landed in one episode's copy and stayed there. The next episode would start from a different ancestor and rediscover several of them. That is the actual cost of a high marginal price: not the extra work of setting up instance N, but the fact that improvements stop compounding. A pipeline gets smarter every run; a template gets copied every run.