Edge System Map: Variables, Pipeline and Data Model

This reference teaches what rules can read, how quotes and orders move through Edge, and how Order, Decision and Execution records relate.

Variables

The read-only variable registry documents type, range, scope, update cadence and use in Routing, Order policy, Automation and Alerts. Update cadence matters: values may be per-order, real-time, per-tick, periodic, T+1 or on-change.

Pipeline flows

Quote flow runs from LP price through Symbols/Sessions, Liquidity, Quote rules and Pricing overrides to client bid/ask. It is stateless, so use time-stamped Ticks for historical evidence.

Order flow runs through Session check and Routing. STP goes to LP without MCB; B-Book proceeds through Order rules and only MCB mode uses the full MCB pipeline; Reject produces no execution.

Data model

Order stores raw order facts and updates remain/status as fills complete. Decision log is an immutable routing-time snapshot. Execution is one-to-many: partial fills and failover can create several terminal fill or timeout rows.

A session-stage rejection may have no decision row. A rejected route has a decision but no execution. MCB fields are null for STP. These are valid path outcomes, not automatically missing data.