Production compiler
The plan is where continuity is decided, not where it is checked.
A shot that inherits the right references, the right story state and the right voice track starts correct. A shot assembled by hand from a spreadsheet starts as a guess that QA has to catch.
01 / Inside the workflow
The units it emits
Tosheo uses one production hierarchy across both launch solutions. A serialized season and a branded campaign arc differ in their content and their approvers, not in their shape, which is what lets the same compiler, router, repair system and delivery packager serve both.
- 01Production
The greenlit unit. Carries the brief, the canon, the rights positions and the budget authority.
- 02Deliverables
What has to be handed over: the episode or master, each language and market track, and each platform version or cutdown.
- 03Sequence
A run of scenes that completes one movement - a homecoming, a confrontation, a product reveal.
- 04Scene
One location, one continuous stretch of time, one set of participating cast with a known story state.
- 05Shot
The smallest unit that can be generated, reviewed, rejected and replaced without disturbing its neighbours.
02 / Inside the workflow
What inheritance means in practice
When the compiler emits shot 04 of a scene, that shot does not contain a description of Anaya. It contains a reference to her approved identity at the canon version this episode inherited, her costume state as of this story day, what she currently knows, the location layout that was approved for the family room, and the position of the doorway established two shots earlier.
That is the difference between a shot list and a compiled shot. A shot list tells a person what to make. A compiled shot tells the system what this unit is allowed to contain.
A close-up on Kabir as he decides not to answer a simple question. The keepsake is on the table between them.
- Inherits identity
- Kabir, approved reference set
- Inherits state
- He knows who wrote the letter. She does not.
- Inherits geography
- Doorway camera-left, as established in shot 03
- Inherits props
- Brass keepsake, on the table, in frame
- Inherits voice
- Approved voice reference, Hindi primary track
- Emits
- Framing, camera direction, performance note, audio, continuity requirements
Because the doorway position is inherited rather than re-described, a result that flips it is a mismatch the continuity stage can name. Without inheritance, the flip is only caught if a person happens to notice it in review.
03 / Inside the workflow
The cost estimate is part of the plan
A plan that does not say what it costs is not a plan, it is a wish. The compiler emits an estimate alongside the structure: the proposed render scope, quality level, expected duration and the maximum authorized cost.
That estimate is what the storyboard and cost-authorization gate approves. Creative approval and spend authorization are deliberately separate decisions - approving a storyboard does not release a budget.
- Estimated variable cost for the proposed scope
- The maximum the router is authorized to spend
- Which shots dominate the estimate, so scope can be cut where it actually helps
- Expected generations per accepted shot, so a re-plan is possible before spending
- Reviewer time the plan will require, because operator cost is part of cost per accepted minute
04 / Inside the workflow
What the compiler will not decide
Questions
Before you bring it into production
Can I bring my own script instead of having one compiled?
Yes, and many productions should. An original screenplay, a web serial, a novel chapter or a series bible can be imported as the input. The compiler then does the part that is genuinely mechanical: turning approved text into sequences, scenes and shots that inherit canon correctly.
How is a branded campaign compiled differently from a season?
The hierarchy is the same. A campaign arc compiles to six to ten connected episodes or story assets rather than a twenty to sixty episode season, adds product moments and substantiated claims as first-class units, and emits derived platform versions from the approved master rather than as separate productions.
Does the compiler decide how many shots a scene gets?
It proposes a count bounded by the brief. Episode length, format and the authorized ceiling constrain what it is allowed to emit, and the proposal is reviewed at the plan gate. If the estimate is too high, the honest fix is usually fewer shots rather than cheaper ones.
What happens if the script changes after the plan is approved?
The affected scenes recompile and the gates that depended on them reopen. Scenes the change does not touch keep their approvals and their accepted shots. This is the same scoping rule canon changes follow, and it is the reason both are versioned.
Does the plan include the language tracks?
Yes. Tracks declared in the brief are compiled as tracks of the same production, with their own voice, pronunciation, caption and native-review requirements. They are not separate projects and they do not get planned after the fact.