08 / 12 Targeted repair

Fix the detail. Protect the approved work.

Keep the correction as small as the problem allows.

A region, a frame, a shot, an audio segment, a subtitle or one derived version. Tosheo repairs that unit and keeps everything already approved around it, along with the relationship between the original, the repair, the approval and the final deliverable.

Free planning. Scoped, paid rendering after approval.

Illustrative production view
Choose an illustrative production scenario

One detail. One scoped correction.

AI-generated illustration of a creative director developing an original storyIllustrative correction scope
Accepted work
Shots 01, 02 and 03
Affected unit
Hand region / shot 04
Preserved track
Approved Hindi audio
Replacement
Awaiting review

A replacement inherits context, not approval.

Fictional example. Explore the workflow; these controls do not render media, approve work or authorize spend.

01

Accepted neighbouring work preserved

02

Original and replacement linked

03

A separate review for the repair

One core. Two launch solutions.

Built around the work you need to deliver.

Targeted repair

Regeneration is the most expensive way to fix a small mistake.

It costs the render, it costs the review of everything it touched, and it introduces new variance in shots that were already right. Repair is narrow on purpose.

01 / Inside the workflow

The blast radius problem

In most generation workflows the smallest thing you can change is the thing you generated. If the episode was generated as an episode, the smallest fix is an episode. One wrong hand in one shot costs the whole run, and the new run is not identical to the old one, so shots that were fine come back different and have to be reviewed again.

That is the blast radius, and it is why correction costs compound. Tosheo attacks it by making the unit of generation, the unit of review, and the unit of repair the same small thing.

RegionSmallest visual repairPart of a frame
ShotStandard repair unitReviewed and replaced alone
SegmentAudio repair unitA line, not a track
VariantDerived repair unitOne version, not the master

02 / Inside the workflow

Versioning that keeps the relationship

A repair is not a replacement that erases its predecessor. Tosheo keeps the original, the repair, the reason, the approval and which deliverable ended up carrying which version.

This matters for three separate reasons, and only one of them is creative.

Creative
You can go back. A repair that made things worse is reversible because the accepted original still exists.
Rights and provenance
The delivery manifest has to state how the delivered version was made. If the repair used a different provider or a different reference, that is part of the record.
Economic
Generations and repair attempts per accepted shot is a cost metric. You cannot manage it if repairs overwrite their own history.
Fictional exampleOne hand, one shot

Shot 04 is right in every way except that Kabir's hand is malformed for eleven frames as he reaches toward the keepsake.

Wrong unit
A region, across part of one shot
Repaired
That region, with the same references and treatment
Untouched
Shots 01 to 03 and 05 onward, all still accepted
Untouched
The Hindi voice track for this scene
Recorded
Original, repair, reason, approver, final deliverable

The episode does not re-render. The neighbouring shots do not need re-review. The audio is not re-timed. The cost of the fix is close to the cost of the thing that was wrong, which is the only sane relationship between the two.

03 / Inside the workflow

Repair without collateral change

A repair that fixes the hand and changes the lighting has not succeeded. Repair success without collateral change is tracked as its own production-quality metric for exactly this reason.

Keeping a repair narrow is why the locked treatment from provider routing matters. Reproducing the conditions of the original generation - same provider, same parameters, same references, same canon version - is what makes a narrow repair possible at all.

Questions

Before you bring it into production

Can I replace one shot without remaking the episode?

That is the core design goal of this system, and it is the single capability that most distinguishes a production system from a generation tool. The shot is the unit of generation, review and repair, so replacing one leaves its neighbours and their approvals in place.

Will a repair look different from the shots around it?

It should not, and that is measurable rather than a matter of hope. A repair reproduces the provider, parameters, references and canon version of the original, and repair success without collateral change is one of the metrics we track. Where a repair does not match, it is rejected like any other unacceptable result.

What happens to the original when a repair is accepted?

It is kept. The delivered version is the repair, but the original, the reason for the repair and the approval chain remain part of the production record and the delivery manifest.

Do repairs count against my authorized budget?

Repairs needed because a provider failed or returned an unusable result are a Tosheo cost. Repairs that come from a change of mind are a scope change and are estimated like any other scope change. The distinction is recorded, not argued about at invoice time.

Can a subtitle or one language track be repaired on its own?

Yes. A subtitle, an audio segment, or one market variant are all repairable units. A pronunciation problem in one track does not touch the master or the other tracks, which is the practical benefit of treating languages as tracks rather than separate projects.

Connected by design

The next decision has context.

Explore all 12 features

YOUR NEXT PRODUCTION

Bring the ambition.
Keep control of the work.

Start planning for free through the brief, canon, storyboard and animatic. Full-quality rendering is a paid, scoped engagement with explicit cost authorization.