A7

The own-workflow ladder, submitted as four graph files someone else in the room could actually read.

Week 7 · Due 23 April 2027 · 3%

A graph nobody else can read isn’t finished, whatever it renders.

What to do#

Rebuild this course’s supplied graph across all four tiers from this week’s exercise, on one held-constant shot: the bare graph as a baseline, the graph plus reference anchoring, the graph plus an upscale and fix pass, and finally a two-stage pipeline that generates a keyframe in one graph and hands it to a second graph that turns it into video.

What to submit#

All four graph files, each one’s output, and a short note naming, for each graph, which of the four node jobs — loader, conditioning, sampler, fix pass — its difference from the baseline is doing.

How it’s assessed#

Graph legibility checks whether the note correctly names the job each difference is doing, and whether someone other than its author could follow the graph file cold. Editing judgment checks that every graph is an edit of one you already have — a node job added, swapped or taken out, and the note saying which — rather than a rebuild from an empty graph each time. Not necessarily the tier below it: these are four shapes off the same baseline, not one chain, and the upscale pass edits the baseline rather than the reference build sitting between them. Range across the pipeline checks that the two-stage top tier actually demonstrates a keyframe handed into a second, distinct graph, not the same graph run twice.