Examples

Every pipeline below is a shape you can build on the canvas in a minute or two (Factory → Workflows → New → Blank canvas), or describe to the command palette and have it drafted for you: "set up a pipeline that…" creates the graph as a free draft you review before running. The node reference explains each block; this page shows how they combine.

Four of them open on a real canvas. Where you see Show it live below, the shape gets drawn onto your own node canvas exactly as the app would build it, ready to run once you've filled in the parts only you can supply — your brief, your templates, your creatives. Nothing runs and nothing is spent until you press Run pipeline.

The reviewed campaign

The default shape — what a plain brief runs if you never open the canvas:

Templates → Brief → Build → Score → Route(overall ≥ 75) ─→ Board "Approved"
                                                        └→ Board "Needs review"

Templates finds the layouts, the Brief says what the campaign is, Build deals the originals and produces them, Score judges each on its own merit, and the Route pre-sorts the board. Change the threshold on the Route rule, add score dimensions ("Emotional pull", "Conversion likelihood"), or point the two Board nodes at different sections — it's all config on the wired nodes.

A quick batch, no judge

Templates → Brief → Build → Board

When you'd rather judge ten creatives yourself than read ten critiques. This is what the Batch recipe runs.

Variations of one creative

Source → Vary(×5, headline + image) → Score → Route(≥ 75) ─→ Board "Approved"
                                                          └→ Board "Needs review"

No brief, no templates — the seed creative is the input. Pick it in the Source node's library picker; the run works on copies, your original stays untouched.

Two treatments, one run

             ┌─ tpl A ─→ Build "Funny"  (4 originals, "meme voice") ──→ Score (Humor) ────→ Board § "Funny"
Templates ───┤
             └─ tpl B ─→ Build "Serious" (2 originals, "no jokes")  ──→ Score (Credibility) → Board § "Serious"

Pin both templates on the Templates node, then drag each pinned template card into its own Build. Each branch gets its own count, run instructions, judge and section, so it's one run in two voices. Give each Build its own Brief if the branches should say entirely different things.

Show it live on the canvas

The polish pass

You have a finished batch and want it tightened, not rebuilt:

(finished batch) → Edit("no widowed words, keep text off faces") → Brand-fit → Score

Wire the Edit node onto the batch's lane. Because the creatives already exist, every node here mints versions: the edited-and-refitted takes appear beside your originals, scored, ready to compare. Set the Brand-fit to Pick rules… if you only want specific rules (say, widow + overflow) instead of the template's full set.

Show it live on the canvas

The iteration loop

Rounds are wiring, not a setting:

Build → Score → Route(≥ 75) ─→ Board "Approved"
                            └→ Rerun → Score → Route(≥ 75) ─→ Board "Approved"
                                                            └→ Board "Second look"

The weak path feeds a Rerun, which rebuilds each creative using its own critique as direction; a fresh Score and Route judge the second attempt. One wire is easy to miss: with two Scores on the canvas, the Rerun must name its judge — wire it from the first Score's small report port as well as from the Route's else path, so the rebuild is steered by the critique of the judge that scored the originals. The canvas flags it in red if you forget, and the Rerun's config has a "Reads score from" picker that draws the wire for you.

Want a third round? Wire another Rerun off the second Route (and its report wire from the second Score). Every round is visible on the canvas, and every original survives for comparison.

Show it live on the canvas

Route the losers to Delete — carefully

Score → Route(≥ 60) ─→ Board "Keep"
                    └→ Delete

Legal, and genuinely destructive: everything under 60 is permanently removed. This is why Delete is opt-in — leave its "run automatically" unchecked and a launched run stops at the node, letting you eyeball what reached it before you run it yourself. Prefer a Board "Discards" section over a Delete unless you're sure.

Which of my layouts fit this?

Templates("a hero layout for a LinkedIn new-hire post")

A single Templates node is a complete, runnable pipeline. It resolves its picks, mints nothing, and the run finishes: an answer, not a batch. Set Search in to both to include the shared system library when your own shelf is thin.

Show it live on the canvas

One creative takes its own path

Any batch, any of the shapes above — then drag from a single promise card into its own node:

Build (6 originals) ──→ Score → …            (5 continue here)
        └─ original #3 → Copy("only this one in French") → Board

The wired creative genuinely leaves the batch — the main Score sees five — and it works before anything is built, as long as the creative is nameable ahead of the run (pinned templates, picked seeds, and versions of either).