Overview

Think of SereinFlow as a path from design to execution:

Project → Flow → Nodes and connections → Saved version → Run → Results

Term	Meaning
Project	A place for flows and their node libraries.
Flow	The execution steps you draw.
Node	One action in a flow.
Version	Flow content saved or published at a point in time.
Run	One actual execution of a flow.
Public interface	A stable entry point for external callers.

Suggested reading order

1. Projects and flows: where the canvas is saved.
2. Nodes and libraries: what actions a flow can perform.
3. Versions and publishing: editing versus externally callable content.
4. Runs and results: what each execution records.
5. Debugging: investigate a flow step by step.
6. Public interfaces: expose a published flow.
7. Environment and keys: capacity and access control.

Each article explains a feature and points to its current endpoints. Use the API reference for endpoint details.