Processes

How AI Videos discovers, reviews and publishes videos, with the decisions and dependencies along the way.

Hover, focus or tap a step to see its details and highlight the matching view. Numbered arrows show branches and loops. This describes the workflow, not a live run.

Flowchart

Pseudocode

- Continue 02
- Resume or start 03
- Confirmed / none 04
- Still uncertain 16
- Ready 12
- Need more work 05
- Enrich missing facts 06
- Eligible 07
- Not eligible / retry later 14
- Accepted 08
- Rejected / blocked 11
- References ready 09
- Required reference blocked 11
- Each completed image 10
- One failure 11
- Passing packet 12
- Failed candidate 11
- Unrelated ready items 12
- Other work 14
- Verified 13
- Uncertain / shared conflict 16
- Continue this batch 14
- Separately scheduled 17
- Later authorized resumption 01

Automation instruction. Read the current instructions and recover actual saved state. A previous completed batch is not the result of this new invocation. An owner pause or stop takes precedence.Instruction and code. Resume the exact unfinished run. Otherwise prepare one new ordinary batch with ten new and five historical publication targets. Resumed targets stay pinned. An explicitly requested source campaign uses its own selected scope instead.Code enforced. The read-only recovery command recommends exact pending publication before new work. Preserve its result and ownership when uncertain. The automation must execute the recommended action; recovery does not run it automatically.Instruction and code. Ready packets and packet creation for reviewed images take priority over unrelated preparation. A complete profile may go live before its source video. A ready group can contain just one item; five is a maximum, not a waiting target.Code enforced. Use the existing local inventory and published catalogue directly. Save discovered IDs before metadata requests. Keep one current source checkpoint, retain unfinished progress and clear completed pagination-token lists. Discovery alone does not publish videos.Code enforced. Requests use server-side workflow key access and existing budgets. Only a successful API response that omits an ID proves unavailability. Access or transport failure preserves records. Upcoming or unresolved videos stay out of processing; eligible duration is 2 minutes through 2 hours 30 minutes.Instruction and code. The automation reviews the evidence and supplies the summary, people, topics and publication metadata. Submission validates the record before image work. Missing evidence stays incomplete; a title alone is not a review. Rejected or deferred slots may be filled from eligible same-lane inventory.Instruction and code. Existing verified originals supply likeness without repeated appearance research. Diffused images are never generation inputs. Only people actually depicted in a thumbnail require portrait references before that thumbnail. Retain other verified relationships without broken profile links or placeholders.Automation instruction. Use the concurrency the tools actually support, without sub-agents. A first portrait feeds only its dependent thumbnails. Do not wait for every candidate to finish analysis, and do not lose successful siblings when one call fails. Retain handles for uncertain calls.Instruction and code. Review identity, readable headline, image quality and provenance under the current image rules. Use the existing targeted retry for a hard failure. Soft warnings alone do not block a serviceable thumbnail. A reviewed video always needs its passing thumbnail; optional unfinished profiles do not hold it.Instruction and code. A failed image affects its candidate or thumbnails that depend on that portrait. Persist passing sibling results. Never turn an unknown result into success or blindly repeat it. Shared publication uncertainty follows the shared hold branch instead.Instruction and code. The caller requests publication as items become ready; code validates each release and serializes the publisher. Save media locally, register it and activate the website changes. Profiles do not consume video quotas. Keep the exact pending release if its outcome is uncertain.Instruction and code. A replacement keeps its new original visible while the exact previous original and derivative are removed. Temporary local cleanup needs no new Hosting grant. Keep references until all dependent calls finish, and retain evidence needed by unresolved work.Instruction and code. Continue the current batch: publish ready items first, finish preparation, resolve candidate work and settle operations. Upcoming candidates remain queued for their due retry. Finalization refuses unfinished preparation, undeferred candidates, unresolved operations or publication ownership.Instruction and code. The code checks terminal run state. The automation is instructed to stop after this invocation’s batch and report truthfully, including quota shortfalls. The next scheduled invocation can resume unfinished work or start its own new batch.Instruction and code. Whole-run stops are for owner direction or shared problems that prevent further safe work, such as uncertain publication or a conflicting publisher. They are not the response to an isolated failed candidate. Do not restart or change schedules to work around a blocker.Code enforced. AI Videos does not wait for this separate workflow. Display the original until its one verified derivative is available. Each image has only its current original and at most one derivative. Replacement removes the previous pair; a failed generation leaves the currently served image intact.