The screenplay is written here — and nothing downstream may overrule it.
Five independently authored configurations inform how that page is staged — never what happens in it. Once written, the page is the fact: resolution reads it per beat into a single machine-readable object, and everything downstream, from the beat to the finished cut, is a build of page and configuration together, never a document someone edits.
From Whiteboard to Launch
Configurations
5
Character and setting authorities, the corpus, the standing instruction, the argument. Separately owned; read-only downstream.
Gates
5
All fail closed. Two terminate in a person rather than a score.
Composition
221 → 1
Beats compose upward into 30 units, five acts and one cut. Nothing composes downward.
Bands fully built
3 of 6
Three are marked PARTIAL on the diagram, and the badges are the point. Ports intact
The operating model
Authority at the top, and only at the top
Most generative production runs the other way round. Someone writes, someone else prompts, and consistency is a matter of how carefully the second person read the first. That works for one image and stops working at scale — because the thing being asked to stay consistent lives in prose that no build step can read.
Character and setting authorities, a citation-addressable corpus, a standing instruction and the author's argument are each maintained separately, by a single owner, and are read-only to everything below them. They inform how the screenplay is written — never what happens in it. Once written, the page is the fact: a resolution layer joins it to those configurations, per beat, into one object the rest of the pipeline consumes. Nothing below the authority line is ever hand-edited — a build artefact whose authority has changed fails its conformance check and is rebuilt, which means correction happens upstream or it does not happen at all.
What holds the structure up is an evidence precedence order. For any statement the system takes the most-documented available version and descends toward invention only when the record will not supply one. Invention is not forbidden; it is labelled, and it is always the last rung reached. That ladder runs the full height of the diagram because every band has to touch it — it is not a policy stapled to the front of the process, it is a component of it.
How to read it. Flow runs downward: configuration, the page, resolution, assembly, gates, render. The spine on the left is the precedence order, heaviest at the bottom, with a connector into every band. Dashed lines in the alarm colour are counter-flow — rejection routing work back to the authority that produced it. Each band and each gate carries its own status badge, and the badges are honest: three of the six bands are marked PARTIAL and two of the five gates are not fully built. A process diagram claiming a finished pipeline would be contradicted by the quality section two clicks away.
← Scroll the diagram sideways to see the full width.
The screenplay is written first, informed by the configurations but never dictated by them. Once written, the page is the fact: resolution joins it to those configurations, per beat, into a single machine-readable object, and everything downstream — beat, scene, act, cut — is a build, never a document someone edits. An evidence precedence order holds the structure up: the most-documented available version of any statement wins, and invention is labelled and always the last rung reached.
What this diagram deliberately does not show. The staging layer's field set and its routing rule — that intent is routed by visibility is legible from the output of any careful production; the schema that does the routing is not. Which invariants the conformance checks cover — the set of failure modes expensive enough to automate is the institutional knowledge. And the resolution layer's precedence rule when two authorities disagree, which is the hardest thing in the system and is unstated on purpose.
The rest is on the board because it is the credential rather than the moat: five co-equal registries, an evidence ladder, gates that fail closed, and correction that only ever happens upstream. A reader has to accept those four before the published gaps read as rigour rather than as an unfinished project — which is why the quality section names its own failures instead of its strengths.
What actually transfers. The configuration set is subject-agnostic: a corpus, a cast, a place, a standing instruction, and an argument. Swap those five and the same machine runs against a different subject. The film is the proof, not the product.
Figures on the diagram — 221 beats, 30 units, five acts, six adjudication statuses — were re-derived against the project repository on 3 September 2026. Where a count here and a count in the repository disagree, the repository is the fact and this page is the bug.