Lessons+

Lesson 1.1

Designing the graph

Workflows architecture: single-purpose nodes, swappable inputs, and graphs that document themselves.

Notes

A production pipeline is a Workflows graph designed on purpose: every node single-purpose, every input swappable, the whole thing legible to a teammate who has never seen it.

Design rules

  • One job per node — a node that generates and upscales cannot be debugged.

  • Inputs at the edge: the things that change per run (reference photo, copy, SKU) enter through input nodes only.

  • Templates inside: locked prompts live in the graph, not in anyone’s chat history.

The three graphs every team ends up with

  1. Product: reference truth → scene → angle batch → upscale → export.

  2. Ad: brief fields → structured prompt → model variants → captions.

  3. Film: storyboard frames → image-to-video per shot → sequence export.

A production graph: inputs at the edge, templates inside

If swapping one input node re-runs the whole deliverable, the graph is designed. If it needs a human ritual, it is a demo.

References

No further reading on this lesson yet.

Resources

No downloads attached to this course yet.

That was lesson one, free.

Join the academy to carry on through the module, keep your progress, and take the resource packs with you.

Join the academy

Free. No card, no charge.