Greenlight brief
Most AI production overspend happens before the first render.
Not because generation is expensive, but because nobody wrote down what "finished" means. The greenlight brief is the object that answers that question once, in a place the rest of the system can read.
01 / Inside the workflow
What the brief fixes
A production brief in a chat thread is a suggestion. A production brief as a structured object is a constraint the system can enforce. Tosheo treats it as the second kind.
Every field below has to be filled before a production can leave the greenlight stage. Fields that are genuinely unknown are recorded as unknown, which is different from being left blank - an unknown rights position, for instance, blocks delivery later rather than surfacing on the day of the deadline.
- Customer and buyer
- Who is paying, and who has to accept the finished work. These are frequently not the same person, and the difference is where late rework comes from.
- Audience and intended outcome
- Who watches this, on what surface, and what they should do next. For serialized work that is usually the next-episode action. For branded work it is the campaign metric agreed in this document.
- Format and deliverables
- Aspect ratio, episode length, episode count, master plus derived versions, caption requirements and disclosure requirements.
- Language and market tracks
- Which languages ship, which markets they ship to, and who reviews each one natively. Tracks declared here are part of one production, not a second project.
- Budget and ceiling
- The estimated variable cost and the maximum authorized cost. The second number is the one the router is not allowed to cross.
- Rights assumptions
- What the customer claims to own or control, and what still has to be cleared. Assumptions recorded here become checkable obligations in the rights ledger.
- Accountable approvers
- A named person per gate, with a role. Not a team, not a distribution list. A gate without a name on it does not close.
02 / Inside the workflow
Why this is a blocking gate rather than a form
Generation cost is variable and compounds quietly. A season is not one expensive decision; it is a few hundred cheap ones, and the expensive part is discovering in week six that the deliverable specification was wrong in week one.
Making the brief a blocking gate means the cost of being wrong is paid at the cheapest possible moment. Changing the aspect ratio in a brief costs a conversation. Changing it after ninety shots are accepted costs the ninety shots.
- Lives in a doc, a deck, or a thread
- Read once at kickoff, then diverges
- Scope changes are remembered by whoever was in the meeting
- Overspend is discovered in the invoice
- Nobody is individually accountable for acceptance
- Lives in the production, versioned
- Read by the compiler, the router and the delivery packager
- A scope change reopens only the gates it actually affects
- The ceiling is enforced before the job is dispatched
- Each gate carries a named approver and a timestamp
03 / Inside the workflow
What an approved brief unlocks downstream
The brief is not filed away after approval. It is the input that several other systems read, which is the practical reason for insisting on structure rather than prose.
- 01The planning compiler reads the format
Episode length, episode count and aspect ratio determine the beat structure, the scene budget and the shot count the compiler is allowed to produce.
- 02The canon reads the cast and world scope
Three principal characters and four recurring locations at launch is a brief-level constraint, not a technical one. The canon enforces what the brief authorized.
- 03The rights ledger reads the assumptions
Each claimed ownership becomes an obligation with a state. Unresolved blocking obligations stop rendering or delivery rather than being noticed at handover.
- 04The router reads the ceiling
Provider selection is bounded by the authorized maximum. A job that would cross it requires a new authorization, not a warning.
- 05The delivery packager reads the deliverables
Masters, variants, captions, cover frames and the disclosure requirements in the manifest all come from this document.
04 / Inside the workflow
A brief that caught the problem early
A five-episode Hindi pilot arc for a returning-daughter mystery set in a Konkan railway town. The creator wanted a Tamil track "if it goes well".
- Format
- 9:16, five episodes, 60 to 120 seconds each
- Primary track
- Hindi, with captions and synthetic-media disclosure
- Additional tracks
- Tamil declared at greenlight, not deferred to post-production
- Rights assumption
- Original premise owned by the creator; one folk melody unresolved
- Ceiling
- Authorized maximum set for the pilot arc only
Declaring Tamil at greenlight changed casting: the voice selection had to survive two languages, so the approved voice reference was chosen against both. Had the track been added after the Hindi master was accepted, the Tamil version would have needed a different voice and the two would not have sounded like the same character.
05 / Inside the workflow
What the brief does not do
- It does not authorize spend by itself. Cost authorization is a separate gate after the storyboard.
- It does not clear rights. It records assumptions that the rights ledger then has to resolve.
- It does not lock creative. Canon, script and storyboard each have their own approval.
- It cannot be approved by automation. Nothing in Tosheo can silently greenlight spend.
Questions
Before you bring it into production
Can a production start without a finished script?
Yes. The greenlight brief needs a premise, an intended outcome, a format and named approvers. It does not need a completed script. Scripts are produced by the planning compiler and approved at their own gate, which is deliberately later and cheaper to revise.
What happens if the scope changes after greenlight?
The brief is versioned, and a material change reopens only the gates the change actually affects. Adding a language track reopens the localization and delivery gates. Changing the episode length reopens the plan, the storyboard and the cost authorization, because all three were derived from the old number.
Who is allowed to approve the brief?
A named person with a production role, recorded against the decision with a timestamp and the version they approved. Automation can draft a brief and check it for missing fields, but it cannot approve one. That restriction is the human-control rule and it applies across every gate in Tosheo.
Does the budget ceiling stop production if a render fails?
Provider failures are not charged to the customer, so a failed generation does not consume the authorized ceiling in the way a successful one does. Retry cost is accounted for as a Tosheo cost, which is what keeps the incentive to route well on our side rather than yours.
Is the brief the same for a serialized season and a brand campaign?
The object is the same and most fields are shared. A branded campaign adds substantiated claims, prohibited contexts, product and packaging references, and a brand or legal approver alongside the creative one. That shared structure is the point: the second solution is configuration on the same core, not a separate product.