Documentation
How flowRS works, what every node does, and how the pieces connect. The node
reference and the knowledge graph are generated from the running registry — the same
one the editor's palette reads — so they describe what actually ships. The editor's palette holds 322 widgets: 273 built into flowrs-core and 49 from the neuroscience libraries (flowrs-neuro, flowrs-neuroviz) it installs beside them. 0 widgets generate a seam: the emitted Rust compiles, then panics at unimplemented!. 16 are stand-ins: the program compiles and runs, but a deterministic substitute answers in place of the model or device the node is named after. 306 ship: no seam and no stand-in. Of the palette's 419 nodes (97 language primitives and 322 widgets), 412 run in the browser as you draw: 396 compute there what the exported Rust computes, and 16 of them are stand-ins. 7 run only in the exported program, and the palette marks each of those, with the reason, before it is dropped. The node reference marks the seams, the stand-ins and what runs only in the exported program.
Node reference
Every node, its ports and its parameters — generated from the registry.
Knowledge graph
The whole library as one map: pillars, nodes and how the signal flows between them.
Form contract
What every export guarantees, property by property, and the FORM.json schema each one ships.
Document format
The published specification of a graph, as a .flowrs document and as text, with its JSON Schema and conformance corpus.
Overview
Guide
Quick start
Guide
AI integration
Guide
Agent runtimes over RAP
Guide
Agent threads
Guide
Node library
Guide
What does this firmware do?
Guide