Learnings · Case studies · Updated Sep 2026
What this programme has learned, written down as it happened.
Every entry below is dated, traceable to the project register, and published whether or not it flatters the build. Several document failures I caused. That is the point: a programme that only ever reports its successes is not producing evidence, it is producing marketing.
Long-form audits of a single problem, with the method and the numbers shown.
Two plates, one shot
The first moving shot of the film, eight seconds of it, and the single-image tests that earned it. A ruling the pipeline was never putting in front of the model, a tidy hypothesis about the paper border that was tested and came back backwards, and the short edit instruction that finally produced two frames close enough to stitch.
What it foundA reference plus a whole-scene prompt re-interprets; a reference plus a short edit instruction copies and obeys the one change. And a pixel metric across a whole frame grades the landscape, not the two men standing in it.
The Kerosene Lamp Problem
Six of nine audited frames contained a lit kerosene lamp in a film set between 1813 and 1821 — a fuel not distilled until 1846. Every prompt forbade it by name, every time. Nine frames scored pixel by pixel against seven criteria drawn from existing project rules.
What it foundProhibitions do not work on this model. Every rule written as “do not draw X” scored below half; every rule written as a positive description, or enforced in code before the prompt existed, passed.
Five failures, and the control each one shipped
Five dated failures on the programme, each traced to its root cause and to the reusable control it produced: a fabricated research return, an audit that reported the rule as the violation, two verdicts condemned by one source's silence, a correction stamp that outlived its correctness, and thirteen delegated tasks superseded by one command.
What it foundThe defect was in the input, not the instruction. A check nobody reads is not a check. Absence of evidence is not evidence of absence.
How the system is built, governed and staged. Standing references rather than dated write-ups.
Operational design
The screenplay is written at the top and nothing downstream may overrule it. Five independently authored configurations resolve per beat and compose upward into scenes and acts.
Feedback funnels
The storyboard’s member-feedback feature, drawn beside a product team’s customer-feedback operation. One funnel, two vocabularies; drag the diagram and only the nouns change.
Quality control
Forty-eight live controls across eight governance domains, the four-level output gate, and an honest account of what the controls still do not catch.
Where we stand
Everything runs to two gates and neither of them is a date. Eight stages in the order material moves through them, and the four open items that decide what happens next.
Dates and register ids correspond to live entries in the project repository. Source IP: Aaron Zeanah, “The End of the Alabama Frontier,” International Journal of Interdisciplinary Social Sciences, Vol. 6, No. 4 (2012).