stroblme d4a1b1db47 History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

..

flows.md

Capability report: PUT /devices/{id}/report, a Capabilities section, offline devices degraded

2026-10-16 17:37:49 +02:00

runs.md

History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

state.md

docs

2026-10-13 10:02:20 +02:00

values.md

Flow inputs carry an origin hint, run or panel

2026-10-15 10:08:46 +02:00