Decision Stream¶
What is this?¶
The real-time stream of order decisions and outcomes. It provides operational evidence; it is not an approval or order-modification screen.
When do I use it?¶
To confirm live flow at shift start and to investigate a rejection, timeout, rapid-close pattern, large order or client dispute.
What should I look at?¶
Order ID, account/UID, symbol, side, volume, server time, request context, decision/result and the visible reason or evidence fields.
What is normal?¶
Records arrive continuously, timestamps are coherent, and results can be matched to the relevant order and account context.
What looks wrong?¶
Repeated rejections or timeouts, missing or delayed records, a cluster by symbol/client/time, or a result that conflicts with related evidence.
What do I do next?¶
Build a timeline. Preserve identifiers and the visible decision record, then compare quotes, connection health, client stream and order context for the same period.
When do I escalate?¶
Escalate material client impact, clustered failures, missing evidence, repeated unexplained outcomes or suspected wider degradation. Never modify or cancel an order without specific authority.
Quick Check¶
Three rejections share one symbol and minute. First determine whether the pattern is isolated to an account, rule context, route or wider market condition; do not assign a cause from the result label alone.