Shot inheritance is the practice of passing locked project decisions into each shot automatically. A shot can inherit script beats, character references, location state, visual style, aspect ratio, and continuity notes without the team restating them manually. Generation becomes additive: the shot prompt only describes what is unique to that shot, while everything else flows down from the project source of truth.
Shot inheritance is the mechanism behind script to video, in parallel — it’s what lets script, look, cast, and shots all move forward together inside one project.
What it looks like in practice
A shot in the second act needs the protagonist in a kitchen at dusk, lit warmly, in 16:9. With inheritance: the shot references the locked protagonist, the locked kitchen location, the project's 'warm dusk' lighting preset, and the project's aspect ratio. The prompt for the shot only describes what is unique — say, 'mid-shot, character pouring coffee, gentle smile.' Everything else flows down. Without inheritance, that shot prompt has to restate the character, the location, the lighting, the aspect, and the style every time — and any one of them can drift.
Why it matters
Inheritance reduces prompt rewriting and keeps shot generation aligned with the project source of truth. It also makes downstream changes safe: update the locked location once and every shot that inherits it picks up the change.
How GATA handles it
Each shot in GATA is a small additive layer on top of project, location, and cast records. The team writes one short prompt for what's unique to the shot; the structural pieces (who, where, how it should look) flow down automatically. Updating a location once updates every shot that inherits it. The pattern keeps shot prompts short, regenerations stable, and downstream changes safe.