Director Review Board

The Director Review Board — or DRB — is the approval gate for every Actor, Prop, and Set in your project. The Storyboard Node won’t run until the DRB says your assets are ready. That constraint exists for one reason: a weak asset, once propagated into 50 frames, is expensive to fix. Catching it at the DRB stage costs one reshot.

Why the gate exists

Every frame in your storyboard references your approved Actors, Props, and Sets. If the Actor looks wrong, every frame with that Actor looks wrong. If a Set is off-period, every frame in that scene is off-period.

The DRB is where you catch those problems before they propagate.

Without a DRB

A shaky Hero Look gets approved silently. The Storyboard Node renders 40 frames. You realize the Actor is wrong. You reshot. 40 frames rebuild.

With the DRB

The Hero Look sits at the review stage. You reject it, reshot the Actor Node, approve the new version. Then the Storyboard Node runs — once, cleanly, on locked assets.

What the DRB shows

Open the DRB Node from the Flow canvas and you’ll see every asset in the project, grouped by type:

• Actors — each character’s Hero Look and any Wardrobe Variants.
• Props — every object asset.
• Sets — every environment asset.

Each item shows its status: pending, approved, or rejected. The DRB makes the whole project’s asset health legible at a glance — no hunting node to node to check what’s still unapproved.

Approving and rejecting

1. Open the DRB Node. Double-click it on the Flow canvas.

2. Review each asset. Zoom in on every Hero Look, variant, Prop, and Set. Look for the things that will matter in 50 frames — identity, period, lighting consistency, material, scale.

3. Approve what’s locked. Mark solid assets approved. Approved assets are eligible for the Storyboard Node.

4. Reject what’s not. Mark weak assets rejected. A rejected asset blocks the Storyboard Node from running until it’s replaced.

5. Reshot rejected assets. Open the asset’s own node (Actor, Prop, or Set), adjust the description, and generate again. Return to the DRB and approve the new version.

Approve in one pass, critique hard

The DRB works best as a single review session, not a trickle. Gather all your generations, sit down, and be strict. It’s much easier to fix a character before 30 storyboard frames than after.

Reshot from the DRB

You can trigger a reshot directly from the DRB without leaving the node. When you reshot an asset from here:

• The asset regenerates using its current description (edit the description first if the existing one is the problem).
• The new version replaces the old as the hero.
• Every downstream storyboard frame that referenced the old version rebuilds on the next storyboard run.

This is the same reshot workflow as from the asset’s own node — the DRB just gives you a faster path when you’re reviewing many assets at once.

Reshot rebuilds downstream frames

If storyboard frames already exist, a reshot will rebuild every frame that used the reshot asset. That’s the intent. It’s also why the DRB should be thorough — the earlier you reshot, the cheaper it is.

DRB states and the pipeline

The DRB produces a single project-level signal: are the assets ready? The Storyboard Node reads that signal before running.

DRB state	Storyboard Node behavior
Any asset pending	Won’t run — prompts you to finish review
Any asset rejected	Won’t run — prompts you to reshot and re-approve
All required assets approved	Runs freely

Only the assets wired to a scene count toward that scene’s storyboard readiness. You don’t need to approve every asset in the project to storyboard a single scene — just the ones that scene uses.

Related

Actors and Wardrobe Building Hero Looks and variants that will pass the DRB.

Props Single-image object assets and how they flow through the DRB.

Sets Environment assets and how location consistency is enforced.

Generating Frames What happens after the DRB greenlights your assets.

FAQ

Can I skip the DRB? No. The Storyboard Node checks DRB approval status before running. This is intentional — skipping the review is the single fastest way to burn credits on frames you’ll reshot.

Do I need every asset in the project approved, or just the ones a scene uses? Just the ones wired to the scene you’re about to storyboard. You can work scene by scene and approve as you go.

What if I change my mind after approving? Open the asset’s node, reshot, and re-approve. Already-generated storyboard frames that used the old version will rebuild on the next storyboard run.

Can I reject an asset and keep working? Yes. Rejected assets block the storyboard from running, but you can keep editing the Script, reshaping shots, and iterating on other assets. Come back to the rejected one when you’re ready.

How do Wardrobe Variants show up in the DRB? Each variant is reviewed alongside its parent Hero Look. A variant can be approved or rejected independently — a strong Hero Look doesn’t automatically approve its variants.

Can multiple people use the DRB to approve on a team? Team review workflows are on the roadmap. Today, the DRB is a solo-director tool.