Operator orientation
Understand the desk, active profile, market lanes, live state, and safety controls.
Documentation map
Understand the system before you operate it.
Reference areas for the terminal, trading lifecycle, service topology, data contracts, agents, and operational safety.
Choose your path
Start with the boundary you own.
01
Operating the desk
Start with profile scope, lane state, stale-data indicators, and the risk view before enabling automation.
02
Building an integration
Use same-origin BFF routes, preserve session identity, and treat every mutation as a governed action.
03
Diagnosing the platform
Follow the request from browser to BFF, gateway, lane service, and external dependency; do not infer health from missing data.
Service operations
Run health checks, inspect routed services, and diagnose the private infrastructure stack.
Trading lifecycle
Follow discovery, signals, scoring, risk validation, broker mutation, and reconciliation.
Streaming data
Work with same-origin SSE and WebSocket channels for market and operational updates.
Risk and authority
Learn the account checks, lane controls, kill states, and fail-closed execution boundaries.
Agent architecture
See how advisory cards are generated, resolved by lane and symbol, and routed to model channels.
Data and identity
Understand per-user profiles, encrypted broker records, persistence, caching, and audit state.
Platform topology
Trace the standalone web app, BFF routes, gateway, trading engines, services, and brokers.
Safety note
Public reference material describes the operating model. The authenticated desk remains the source of current account, risk, automation, and service state.