Point Visuals and Nodes at the openflowfm/visuals wiki, where they live now
Document cords either way, the on/off switch, and what out is really for Cords can be pulled from an input as well as an output, and dropping onto a taken input replaces the cord rather than refusing it. A transform's title carries an on/off switch that passes its input through while keeping every cord and setting. Out is no longer described as undeletable: a flow without one can still be a provider handing signals out through give. Node previews keep the wall's uniform-bank layout, so an edit cannot leave the two sides uploading different shapes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Codex <noreply@openai.com>
Document the model material showcase Co-authored-by: Codex <noreply@openai.com>
Document model material authoring Co-authored-by: Codex <noreply@openai.com>
Document model preview navigation and lighting Co-authored-by: Codex <noreply@openai.com>
Document live model setup previews Co-authored-by: Codex <noreply@openai.com>
Document the first-class model library Co-authored-by: Codex <noreply@openai.com>
Document reusable GLB models Co-authored-by: Codex <noreply@openai.com>
Document the Xenon graticule form Co-authored-by: Codex <noreply@openai.com>
Document the Xenon vault form Co-authored-by: Codex <noreply@openai.com>
Document the Xenon meridian form Co-authored-by: Codex <noreply@openai.com>
Document the Xenon spindle form Co-authored-by: Codex <noreply@openai.com>
Document Xenon rosette and corolla forms Co-authored-by: Codex <noreply@openai.com>
Document Astrolabe Xenon flows Co-authored-by: Codex <noreply@openai.com>
Document the rounded Gyre form Co-authored-by: Codex <noreply@openai.com>
Document the Xenon armillary family Co-authored-by: Codex <noreply@openai.com>
Document the counter-wound Rotor form Co-authored-by: Codex <noreply@openai.com>
Document the cuboid Truss form Co-authored-by: Codex <noreply@openai.com>
Document the eased Weave tumble Co-authored-by: Codex <noreply@openai.com>
Document the Iris form Co-authored-by: Codex <noreply@openai.com>
Document woven crossings and relief arcs Co-authored-by: Codex <noreply@openai.com>
Document relief and loom forms Co-authored-by: Codex <noreply@openai.com>
Document woven and orbital forms Co-authored-by: Codex <noreply@openai.com>
Document connected trace visuals Co-authored-by: Codex <noreply@openai.com>
Say that light goes past white, and that copies get dealt The node manual regenerates itself, so `vary` and the two new modes arrived in Nodes.md on their own. Visuals.md needed the prose: a neon filament is driven above what the screen can show and `spread/bloom` is what puts that excess back as halo, which is the difference between a lit line and a pale one. `shade` gains `filament` — one colour from unlit to blown — because ramping across the palette paints hue onto geometry and a curve whose colour changes along its length reads as a thermal image. And `vary` is here, with why a copy number wired straight into brightness gives a ramp round the ring rather than sixteen separate lights. Twenty-four flows now: `depth` and `comet` join the five. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SGPm8ZaGY63UWZRkGg2feU
Name the five flows made of glowing line The library table said seventeen and lists twenty-two now. The last five are one family rather than five unlike each other, which is worth saying in the guide along with why: they are the only place the drawing nodes are written down as something you can take apart, and what they are not is a folder of video files — the loop is the beat, the colour is your colourway, and there is no resolution they were mastered at.
Add the drawing nodes to the manual, and the oscillator merge to the guide The node reference is generated, so `figure`, `array`, `glow`, `shade` and `form` arrived in it on their own. The guide is not: it calls out the nodes worth a paragraph, and five new ones with nothing said about them would send a reader to a reference page to work out what a distance is for. So: how a shape becomes a lit line, why `array`'s second outlet is the point of it, and what `form` costs — it brings its own light rather than being bloomed, and turning `chrome` up trades the glow for a reflection of a room built out of the colourway.
Every node, every mode, every inlet — generated from the rig Visuals has a table of what you can drop on a canvas, written by hand and read before you start. This is the other half: the thirty nodes in full, with each one's modes, what every inlet is for, and the value it starts on until you say otherwise. It is generated — `npm run dev:node-manual` in the repo — from the same descriptions the app prints on the node, so the manual and the app cannot come to disagree about what a mode does. The list it joins had said eleven `lens` modes since the twelfth was added.
Document the lineage forest Co-authored-by: Codex <noreply@openai.com>
Document the visual Archive Co-authored-by: Codex <noreply@openai.com>