SQL-Inspired Rules / SQX

SQX is the app's SQL-inspired rule language. It compiles declarations into configured L1 models and conditions into L2 rules. It does not query a database or provide the full SQL language.

Use it for small declarative checks and model configuration. Keep SJS as the main algorithm when decisions need custom state, validation, branching, or order coordination. L3 remains the optional advanced oversight layer.

How a rule reaches execution

1. Each source line is parsed separately.
2. IF declarations configure model instances; conditional lines configure multi L2 rules.
3. On a frame, the applicable L2 rules calculate values and run their matching actions.
4. A SET action changes properties on existing eligible L1 instances. Those instances can run later in the frame.
5. Any resulting order still passes through the surrounding session's execution methods and controls.

A parsed target does not create an order primitive, and a matching condition is not a confirmed fill.

Read in order

1. Getting started: a complete non-transmitting example.
2. Syntax: line boundaries, keywords, parameters, and values.
3. Conditions: comparisons, AND, and current OR limitations.
4. Indicators: registered calculations and data requirements.
5. Actions: targets, final actions, and execution ownership.
6. Working with SJS: frame order and shared controls.
7. Examples: small rules with explicit expected behavior.
8. Debugging: parsing, values, targets, and requests.

The existing syntax entry remains available. These guides describe the current text parser, including its limitations; examples from generic SQL or other rule languages are not interchangeable.

For parameter catalogs and known metadata differences, use the reference guide. Compare environments in the capability matrix, or look up shared terms in the glossary.