OR Logic & Grouping

The current SQX text parser does not reliably implement OR. It splits OR-separated comparisons but compiles a multi-condition group as AND. Parentheses and nested groups are not accepted.

Do not use an OR expression simply because it parses. The structured multi-rule runtime has an OR mode, but the text parser does not preserve that behavior.

Supported text combination

TICK price > 50 AND price < 60 THEN FINAL skipall

Both comparisons must match. This example skips later ordinary L2/L1 work in the tick branch; it does not submit an order or undo an earlier SJS action.

Use SJS for branching

Keep OR, mixed precedence, nested conditions, and readiness checks in the main SJS algorithm. Separate SQX rules can both run and overwrite targets, so they are not an automatic substitute for a grouped expression.

Read SQX conditions, working with SJS, and SJS lifecycle.