Pick one model for the hero take

Pick one model for the hero take. Failover is for drafts. The clip you will actually post, the one legal already nodded at, the one that has to match yesterday’s pack, ships from a single named row. Mixing Veo on take two and Kling on take five because a queue hiccuped is how a face becomes a family of cousins.

The Sora lesson is not “never use one vendor.” It is “do not let the hero live on a row you cannot replace without a new identity.” The Sora app and web ended 26 April 2026. The Sora 2 API shuts 24 September 2026. The migration plan is the checklist. This page is the weekly radio: drafts may shop; the hero may not.

GPT-6 Astra will not make your videos. When a flagship vanishes, you still need a clip row. Pick it on purpose for the take that ships.

Drafts may failover. Heroes may not.

A draft is a blocking test, a prompt debug, a “does this camera move even work.” Silent cheap rows exist for that. Kling 3 Turbo is silent, 1080p, 3–15 seconds, 12 credits. If Turbo is down, another silent motion row is an acceptable failover for the draft. You are not locking identity yet.

A hero is the take that enters the edit as A-roll. Identity is closed: this face, this bottle, this room. The row that produced it is now part of the asset. Regenerating the same prompt on a different family will not give you “the same shot, other vendor.” It will give you a new sample. Seedance is not Veo with a different logo. Kling O3 Pro is not a Sora snapshot.

Failover logic that is safe:

• Same slug, retry. The queue recovered. Identity still belongs to that row.
• Same family, different speed tier, only if you already treated both as drafts. Turbo versus O3 Pro are not the same identity contract; one is silent, one is sounded, and the pictures will not match.
• Different family, only before picture lock. Once the client said yes to a frame, you may extend, edit, or I2V from that frame. You may not “try Seedance real quick” and cut the two together as one person.

Unsafe failover is what people do at 4 p.m. on a Thursday: the hero row is slow, the calendar is red, they generate the same prompt on whatever is idle, and they ship the idle one. That clip will not match the rest of the series. It will not match the still on the site. It will look like a reshoot with a different actor.

Write the hero slug on the slate. Not “Google.” Not “Kling.” The published slug. Veo 3.1 if the hero is a short dialogue take. Seedance 2.0 if the hero is a sounded cinematic hold up to 15 seconds. Kling O3 Pro if the hero is Kling physics with audio. One of those, for this week’s A-roll, unless the job itself changed.

The Sora-shaped risk is identity, not nostalgia

Sora was a single-vendor habit for a lot of storyboard pipelines. When the consumer surface died in April, the API still ran. When the API dies on 24 September 2026, prompts do not port as identity tokens. You cannot paste a Sora board into Veo and keep the same people. That is the lesson to apply this week to every hero, including ones not on Sora: the model is part of the character sheet.

If you are still generating Sora-shaped heroes in mid-September 2026, stop. Migrate the job to a living row and lock that row for the series. Do not limp through the 24th with “one more Sora hero” and a secret backup on Kling. Those are two series.

Platform risk is why a studio catalogs many models. That is good for drafts, for jobs that need different physics, for not living in Flow. It is not a reason to treat the hero as a load-balanced pool. Load-balance the queue. Do not load-balance the face.

A series is one row per shot type, written down:

• Talking hero: one sounded slug.
• Pack turn: one I2V or R2V slug from a locked still.
• B-roll motion: one silent slug if you score it yourself.

That is three radios for a week, not thirty. When a slug dies, you replace the type, reshoot the stills if you have to, and start a new lock. You do not mix old Sora A-roll with new Veo A-roll in one cut and call it a season.

Retries stay on the hero slug

Retries on the hero stay on the hero slug. Five Veo 8-second tries are still Veo. They are not a reason to “see what Seedance does” unless you are willing to throw the Veo takes away. Seeing what Seedance does is a draft. Keep it in a draft bin.

A 4 p.m. queue stall is the usual excuse. The hero row is slow, the calendar is red, an idle family is green. Shipping the idle take as the same person is a reshoot you just published. Wait, ship a different already-locked clip, or I2V from an approved still. Do not sample a cousin and cut it in.

Cap the retries on Monday so Thursday does not invent a second hero family. Two tries on the named slug, then a still-based path or a different shot, not a different actor. Extend and edit after a keeper; they are not new models.

What to write on Monday

Before the first generate:

1. Name the hero clip. There is usually one. If there are three, name three slugs, one each, not a pool.
2. Name the draft slug for blocking tests. Cheap, silent if the test is not the sound.
3. Write “no cross-family cut on A-roll” on the brief so a collaborator does not failover in your absence.
4. If the hero slug is a vendor you would not bet a month on, lock stills now so you can I2V the same identity on a replacement row later. A still is a portable contract. A T2V sample is not.

When the hero lands, stop shopping. Extend if you need time and the last frame is a keeper. Edit if you need a crop or a jacket. Caption and overlay after picture lock. None of those steps are a new model.

The AI video generator will let you change the row every run. That is a feature for the draft pile. For the hero, treat the dropdown as already chosen.

Credits do not argue with this. A cheaper failover that ships the wrong face is a reshoot. A dearer hero slug that matches the series is the cheaper week.

If you need one project with a named hero row and a named draft row, sign up and keep failover off the A-roll. The Sora date is a calendar. The radio is a habit.

FAQ

What if the hero row is actually down?

Wait, or ship a different clip that was already locked on another row. Do not generate a replacement hero on a cousin family and cut it in as the same person. If the calendar cannot wait, use a still-plus-I2V path from an approved frame, not a blank T2V on a random slug.

Can the B-roll be a different model from the talking hero?

Yes. That is a different shot type. Do not match-cut them as one continuous take. B-roll is allowed to look like a different camera. A-roll faces are not allowed to look like a different actor.

We have two heroes this week, Veo and Seedance. Is that “one model”?

One model per hero take. Two shot types may use two slugs. What you cannot do is failover inside a take, or intercut two T2V families as one character. Write both slugs on the slate so nobody “helps” by mixing them.