Flow Editor concepts

These pages explain why the editor accepts some graphs and rejects others. If you are new, read them in the order below and then try the corresponding action in the RSI quickstart. If you already build strategies, jump to the rule you need to verify.

Strategy design

1. Tactical and Portfolio strategies explains the two modes and why their primary triggers and available nodes differ.
2. How a strategy starts and continues explains the primary activation, control outcomes, waits and why canvas placement is not execution order.
3. Nodes, parameters, outcomes and ports names the pieces you see in the canvas and Inspector.
4. Control and data connections explains the two networks in one graph and how types constrain an edge.

For example, Event Trigger can send control to Condition while Indicator supplies an RSI data value to its Left input. Both are needed for a decision. Condition.Match is a control outcome; Condition.Result is a Boolean data output. This distinction matters more than where the nodes sit on screen.

Readiness and lifecycle

• Validation and readiness separates graph errors, warnings and information from Backtest data and plan prechecks. A graph can be saved without being ready to run.
• Saves, versions and checkpoints explains local edits, confirmed saves, read-only history and non-destructive restore.
• Plans and feature availability explains why a node, an option, a Backtest feature or a Quant Hub metric can be visible yet unavailable to the current account.

Reading order

For a first strategy, read modes → activation → node anatomy → connections → validation → saves, then use the guides to make the change. For an existing graph, start at the failing point: connection troubleshooting, activation troubleshooting, or save recovery. The glossary provides short definitions.