Rights ledger
The expensive rights problem is never the one you knew about.
It is the folk melody someone cleared for one platform, in one territory, for one year, and nobody wrote down which. A ledger exists so that the question has an answer before the deliverable is handed over, not after.
01 / Inside the workflow
What the ledger records
A rights position is not a yes or a no. It is a set of bounded permissions, and productions get into trouble when a bounded permission is remembered as an unbounded one.
Each entry in the ledger attaches to a specific asset and answers a fixed set of questions. Unanswered questions are a state, not an absence - an asset with an unresolved blocking right can be planned around, storyboarded and even generated, but it cannot be delivered.
- Ownership and control
- Who owns the source, or who controls it well enough to grant what they are granting. These differ more often than people expect.
- Permitted uses
- What the grant actually allows: production, publication, derivative works, paid promotion, sublicensing.
- Territory and platform
- Where the deliverable may be shown and on what surfaces. A track cleared for one country is a constraint on a market variant, not a footnote.
- Languages
- Whether the grant covers dubbed, subtitled or otherwise adapted versions. A language track can be blocked while the primary master ships.
- Term and expiry
- When the permission starts and ends. Expiry is a date the system holds, not something a person is expected to remember two years later.
- Model restrictions
- Whether a source asset may be used as a reference for generation at all, and by which providers. Some grants say no, and the router has to know.
- Attribution and disclosure
- Required credits, and the synthetic-media disclosure obligations that attach to the finished deliverable.
02 / Inside the workflow
Provenance: where each frame came from
Rights answer what you are allowed to do. Provenance answers what was actually done. Tosheo records the lineage of a generated asset - which model, which prompt, which references, which seed where a provider exposes one, which version of canon it inherited, and who accepted it.
That record is what makes a rights position defensible rather than asserted. If a buyer, a platform, or a regulator asks how a shot was made, the answer is a lookup rather than a reconstruction.
- Model and provider used for each generation attempt
- Prompt, references and canon version the attempt inherited
- Seed and generation parameters where the provider exposes them
- Every attempt, not only the accepted one
- The human who accepted the result, their role, and when
- The relationship between an original, its repair, and the final deliverable
03 / Inside the workflow
How a missing right stops the line
A warning that can be dismissed is a warning that will be dismissed, usually on the afternoon of a deadline. Blocking rights are therefore enforced at two points where stopping is still cheap.
- Rights and source-asset clearanceCustomer, plus a Tosheo rights reviewerBlocks: Generation that depends on the unresolved asset. Other shots proceed.
- Final delivery acceptanceNamed delivery approverBlocks: The delivery package as a whole, including every market variant that depends on the unresolved grant.
04 / Inside the workflow
The Indian production context
Tosheo is built by an Indian company for Indian-language production first, and the rights questions that come up most here are not the ones a generic tool is designed around.
Folk and devotional material with unclear chain of title. Regional music with fragmented publishing. Adaptations of web serials where the visual rights were never separated from the text rights. Spokesperson and likeness permissions that are territory-bound. These are ordinary situations, and the ledger is shaped by them.
- Tosheo will not produce celebrity likeness or cloned voice without verified permission.
- Tosheo will not depict real people, actors or franchises in generated artwork.
- Tosheo will not act as an agent, distributor, financier or rights representative.
- Tosheo will not treat an unresolved blocking right as an acceptable risk to ship around.
Questions
Before you bring it into production
Does Tosheo clear rights on my behalf?
No. Tosheo provides rights intake, a chain-of-title checklist, and a ledger that records and enforces what you tell it. It is a coordination and record system, not a rights representative, and it does not substitute for legal advice. The brief is explicit that Tosheo will not claim to be an agent or rights representative unless the contract, capability and professional advice exist.
What counts as a blocking right?
Anything whose absence would make delivery unlawful or a breach of the grant: missing ownership of a source, an expired term, a territory the deliverable is going to that the grant does not cover, a model restriction on a reference, or a required disclosure that has not been applied.
Is synthetic-media disclosure applied automatically?
Captions and synthetic-media disclosure are on by default for serialized production at launch. The obligation is recorded in the ledger and checked in the delivery package, so an export that should carry a disclosure and does not is caught before handover rather than after publication.
What happens when a licence expires mid-season?
The expiry is a date the ledger holds, so it surfaces as a production issue before it becomes a takedown. What you do about it - renew, replace the asset, or re-cut the affected episodes - is a decision with cost implications, which is exactly why it needs to arrive early.
Can I export the rights and provenance record?
Yes. The delivery package includes cue and rights information, provenance and a delivery manifest. Accepted assets and production data remain exportable, which matters because the record is only useful if it survives your relationship with us.