Unlimited 4K video generation for Pro | Seedance 2.0 Mini is 90% off! Hurry, deal expires in Upgrade Use a base design view, constraint register, and reference sets to establish clearly named option branches with their own themes, shared limits, seed views, and comparison notes.

The actual workflow — connected nodes you can run to preview each step.
Professional capabilities powered by AI.

Prevent early options from becoming unlabeled variations with no clear design proposition.

Give each designer or workstream a defined branch while preserving shared project constraints.

Explain what each direction is testing and which conditions remain constant across A, B, and C.
Branches should differ through meaningful design choices while sharing the constraints required for a fair comparison. If every input changes, reviewers cannot tell which decision produced the result.
Use names that describe the proposition rather than ranking the options. Labels such as “preferred” or “safe” bias the review before the criteria have been applied.
Record when a branch intentionally challenges a constraint or assumption. An explicit exception can support exploration; an undocumented departure creates confusion later.
Set up A/B/C branches that share the project rules while exploring genuinely different propositions.