System Context
Understand how the platform integrates with TradingView, TopstepX, and external systems.
View Context Diagram →Container Architecture
Explore the internal structure: Frontend, Backend, Database, and their relationships.
View Container Diagram →Critical Flows
Detailed flowcharts for live entry, exit/reduce, pyramiding, payout security, and more.
View Flows →Operational Assumptions & Warnings
The platform implements several security-first features that require operator awareness:
- State Freshness: TopstepX risk state is cached for up to 30 seconds (configurable). If state age exceeds 10 seconds, a warning badge is displayed.
- Verification Mismatch: If provided state doesn't match TopstepX state, trading is blocked by default (fail-closed). If fail-closed is disabled, a warning badge is shown but trading continues using TopstepX state.
- Funded Floor Source: When account is funded and MLL is zero, floor balance priority is: TopstepX-reported > Config > Assumed. If floor source is "assumed", a warning badge is displayed requiring manual verification.
These warnings help operators identify when the platform is operating with potentially shaky assumptions and require attention.