Trading Behavior Evidence in Edge

Classic teaches Abnormal Flow, News Event Risk and Account Correlation. This page does not redefine abnormal trading. It teaches where to query a supplied pattern in Edge, how to control scope and what evidence to deliver.

Start with Account / UID + Time Window + Symbol + known Ticket. Preserve the source timezone, then align to Server Time.

Clients: Account→Fix Time Window→Orders: all relevant Tickets→Open selected Order / Decision→Ticks / Events when needed→Related Accounts only with shared evidence→Evidence Summary

1. Use Clients to locate Client/UID, Group and related-account count. Relationship alone does not prove shared behavior.
2. Use Orders with Account, Symbol and Time Window; preserve every relevant Ticket, side, action, type, volume, price, status and time.
3. Confirm Open/Close, Holding Time and P/L in MT4/MT5 History / Closed Orders when Edge does not show the complete fields.
4. Open Decision only for representative or disputed Tickets; record Request, Filled, Client fill, Final, Cost and Status.
5. Use Ticks only for market/quote questions, with exact Server Time, symbol/taker and a narrow window.
6. Use Events to record actual event/timezone overlap.
7. Expand to related accounts only when timing, symbol, direction, size or open/close interval supplies shared evidence. Use UID/IP/Device only where supported and permitted.

Apply this route to rapid open/close, event concentration, sudden large lots, symbol concentration, similar accounts, opposite-direction patterns or Deposit → Trade → Withdrawal. Always preserve the sample window, full Ticket set, field values, unknowns and reason for any scope expansion.

Do not write “Client is scalper” or “AB account confirmed.” Use the Investigation Result, then complete the integrated assessment in Level 6 — Investigation Case Lab.