Mundus ex nodis. the world from nodes · the dag, lucke 2014
LUCKE · 2014 · 2018 · 2021 · TODAY
The procedural is what happens when you replace a stack of edits with a graph of operations. A number flows in. The graph composes. A form flows out. Edit the number — the form recomputes. The graph is the program. The artist no longer keeps a model; the artist keeps a recipe.
The conventional 3D pipeline is a stack: a base mesh, then a modifier, then another, then another, each rewriting the data in place. Edit any step and you re-edit every step that follows. The stack is a list.
The procedural pipeline is a graph. A directed acyclic graph, formally — nodes connected by wires, data flowing in one direction, no cycles. Each node is a pure operation; each wire carries a value (or a function over values, which is a stronger thing). Edit a parameter at any input node and the graph re-evaluates. Same outputs every time, given the same inputs. Determinism by construction.
This is not a 3D idea. It is the function-composition model, drawn. Mathematicians call it f ∘ g ∘ h; programmers call it a pipeline; artists call it nodes. The drawing is the program. The procedural is the graph, made authorable.
Three node-graph systems shipped the same idea through different surfaces. Each one was a Blender addon. Each one taught the platform something it eventually absorbed. The arc spans a single decade and converges in a single name on every commit: Jacques Lucke.
PYTHON ADDONTIME-FLOW
Lucke wrote it as a hobbyist — a German student who wanted Blender to do kinetic typography. The addon let you wire time through math nodes into vertex displacement, and the result was the kind of motion-graphics that takes weeks in After Effects done in real-time on a laptop. The addon went viral on Vimeo and Twitter. Blender hired him in 2018. Specimen 036.
RUSSIAN OPEN-SOURCEPARAMETRIC CAD
The Russian community took the same year and the same platform and built a different graph: the parametric architecture graph. Sliders, polygons, lofts, towers. Сверчок — cricket — became Grasshopper-for-Blender, the open-source cousin of the Rhino plugin every parametric architect knows. Pull a slider; the whole world recompiles. Specimen 037.
NATIVE C++FIELDS PARADIGM
The same author. The same idea. Native this time. Geometry Nodes shipped in Blender 2.92 (Feb 2021) and was then rebuilt in 3.0 (Dec 2021) around a new abstraction: the field. Wires no longer carried values; they carried functions evaluated lazily per-vertex, per-edge, per-face, per-point. The graph never iterates; the engine handles it. Same graph, different result at every position. Specimen 038.
Three substrates, one idea. Animation Nodes is Python. Sverchok is Python. Geometry Nodes is C++. Animation Nodes carries values. Sverchok carries parameters. Geometry Nodes carries fields. The lineage is not a copy — it is a maturation. The same author re-implementing the same conviction at three layers of the stack.
What changed between 2014 and 2021 was not the idea of a node graph. The idea of a node graph in this form was already old — Houdini shipped SOPs in 1996, Grasshopper in 2007, Substance Designer in 2010. What changed is who got to use one. The procedural escaped the technical-director's office.
Three forces moved at once: open-source platforms (Blender) became viable at production scale; community plugin economies matured (Animation Nodes, Sverchok) into testbeds the platform could absorb; and commodity GPUs reduced node-graph evaluation cost from minutes to milliseconds. The graph that took an hour in 2007 now redraws on a parameter slider drag.
The cleanest illustration is Lucke's career. The Blender Foundation hired the author of its largest community addon and asked him to design the engine he'd been prototyping outside it. Geometry Nodes is the second draft of Animation Nodes — same author, native substrate, fields instead of values. The promise was always there. The platform finally let it land.
Plate IX argued that the right answer is often older than the conditions in which it can be used. Plate X argues something narrower and more specific. The right answer is sometimes written by someone the platform hasn't hired yet.
Animation Nodes was written by a German student in 2014 because Blender wouldn't do what he wanted. Sverchok was written by Russian volunteers because Blender wouldn't do what they wanted. Geometry Nodes is what Blender shipped after the Foundation hired the addons' authors and let them rebuild the same conviction natively. The community wrote the future. The platform paid attention.
The discipline of procedural authoring is the discipline of trusting the graph. Don't model the result; describe the rule. Don't keep the data; keep the recipe. Pull a parameter — the world recomputes. The author's job is to write the function, not to maintain the output.