Auto episode generator

Confirming a draft does three things in order. It charges the full price of the episode, every take plus the assembly fee, in one atomic operation. It creates the series if you did not pick one, and an episode record under it with the scene plan. Then it submits each take to the render service and attaches a webhook, so the service calls back when the take is done.

Each callback updates the take. A trigger runs on every one of those updates, counts the finished takes against the scene plan, and when the last one is complete it claims the assembly job, downloads the clips, conforms and joins them, and files the result as the episode.

A button means somebody has to be watching. A trigger means the moment the final take lands, assembly starts, whether that is forty seconds later or at three in the morning. It also means the assembly cannot be forgotten: there is no half-finished episode sitting in a draft state because you got distracted.

The claim step is what keeps two triggers from assembling the same episode twice when two takes finish in the same second. The first one through wins; the second sees the claim and stops.

It will not assemble a partial episode. If any take fails, the episode is marked failed and left unassembled; the takes that did finish are kept as clips. You can re-draft the episode, or cut a shorter version from the finished takes with the manual assemble option.

It will not charge more than you agreed. The price shown on the review screen travels with the confirmation, and the server compares it to its own total before anything moves. If the two disagree, nothing is charged and you are asked to reload.

The drafter casts automatically from whatever is in your library plus the preset roster. There is no casting step, but there is a lever: characters you generate yourself are listed first and the drafter prefers them. Generate a lead you like once and every episode you draft from then on will reach for them.

Outfits, sets and props work the same way. A set you upload, say a photo of a particular kitchen, becomes a location the drafter can name in a scene and the renderer can hold onto across takes.

Webhooks occasionally go missing. A scheduled sweep runs every ten minutes, asks the render service about any take still pending, and finalises it either way. An assembly that was claimed but never finished, because the server instance died mid-job, is caught by the same sweep and marked failed so you are not left watching a spinner.

All of this is invisible when it works, which is the point. The visible surface is one box, one review screen and one episode page.