Launch
5 nodes · 5 surfaces
Product Launch Reel
Hook, hero frame, camera push, CTA ending, and export handoff for fast campaign launches.
Hook-firstHero shotCTA export
Lane
brand
New Flow
Start from real production structure, not a blank graph alone.
The Flow entry surface should make three things obvious immediately: which reusable starts already exist, how many surfaces the system will touch, and where the work goes once the first node is live.
Live Flow Templates
4
Template Nodes
21
Linked Surfaces
7
Reusable Starts
2
Starter Paths
Open the lane that already matches the job.
Each starter below comes from the live flow-template catalog. Node count, lane posture, and downstream surfaces are derived from the same graph definitions used elsewhere in the product.
Open Flow
Video Lane
6 nodes · 5 surfaces
Scenebuilder Continuity
A Google-Flow-like video lane template for ingredients consistency, shot extension, and asset continuity.
IngredientsContinuityShot extension
Lane
video
Identity
5 nodes · 5 surfaces
Character Intro Sequence
Identity lock, style anchor, first reveal shot, runtime continuity, and ship handoff for recurring characters.
Character lockReveal shotRuntime continuity
Lane
character
Flow Ledger
Template mix
2 reusable / 2 guided
Some flows are reusable production structures. Others are guided starting points that lead into the same cockpit.
Surface split
7 creation / 6 production
Flow spans the creative workspaces and the operational surfaces that finish, queue, and publish the job.
Primary launch route
/flow/brand-campaign
Templates hand off into real flow shells first, then into Studio, Queue, and Publish as the work tightens.
Lane coverage
Brand 2 · Video 1 · Character 1
The catalog is grouped by production posture rather than pretending every flow behaves the same way.
Lane Mix
Brand
Flow family
2
Video
Flow family
1
Character
Flow family
1
Audio
Flow family
0
System Handoff
A new flow should immediately reveal the surfaces it will touch next.
Flow is not a static planner. It feeds creation lanes, runtime oversight, and delivery controls. The entry surface should say that clearly before the user opens any one node.
Video Studio
VideoText-to-video generation with quality, camera, and output controls.
Production Studio
ProductionPlan shots, creative direction, and production metadata.
Runtime Control
RuntimeLive render/runtime controls for ongoing production jobs.
Usage Dashboard
BillingInspect credits and generation usage over time.