Workflows
A workflow is a node graph — the graph JSON is the whole artifact.
A workflow is a node graph that produces a fragment shader. The graph JSON — nodes, edges, and their data — is the whole artifact. There is no compiled output to manage: persisting a workflow is persisting JSON, and everything downstream (the editor canvas, embeds, code export) reads that same graph.
Autosave and revisions
The editor autosaves shortly after you stop editing (an 800 ms debounce), and
only when the graph actually changed. Every save bumps the workflow's
revision number, and saves are compare-and-swap on that revision: if the
workflow changed underneath you (another tab, another member), the save is
rejected instead of silently overwriting.
When that happens a conflict panel appears with two choices: reload the newer version, or overwrite it with yours.
Organization scope
Workflows belong to an organization. The workflow browser supports search, sort, favorites, tags, and a grid/table toggle; members of the org share the same workflows.
Archive
Archiving removes a workflow from the browser without deleting it. Archived workflows live on the org's archive page, where they can be restored or permanently deleted.