Skip to main content

HX110 Simulation Risk And Operations

HX110 teaches the operational layer around trading. HyperionX includes local simulation, Chart Trader order handling, OCO behavior, server strategy surfaces, and recovery workflows. Users need to understand those systems before live trading.

Lesson 1: Hyperion Sim Accounts​

Hyperion Sim is the first place to validate trading behavior.

Teach:

  • Starting capital.
  • Reset simulation.
  • Commission per order.
  • Commission per unit.
  • Position state.
  • Open orders.
  • Fills.
  • Local paper account boundaries.

Simulation should model fees and order behavior closely enough to catch sizing, bracket, and workflow mistakes before live credentials are used.

Lesson 2: Order State Model​

Order workflows should not assume only one active state.

Teach users to recognize:

  • Submitted.
  • Accepted.
  • Accepted by risk.
  • Working.
  • Trigger pending.
  • Part filled.
  • Filled.
  • Cancelled.
  • Rejected.

Active order displays, bracket logic, and cancel/flatten workflows should account for provider state differences.

Lesson 3: OCO And Bracket Operations​

OCO behavior protects positions when used correctly.

Teach:

  • The entry order size comes from Chart Trader.
  • Bracket targets/stops are children of the filled entry.
  • A filled OCO child cancels its working siblings.
  • Stop and target sides must be valid relative to the market.
  • Multi-target presets need explicit size allocation.
  • Moving stops to breakeven should happen once, not repeatedly.

Users should test every OCO preset in simulation.

Lesson 4: Risk Tools​

HyperionX risk training should include both UI and chart tools.

Teach:

  • Position size.
  • Notional value.
  • Leverage.
  • Required margin.
  • Estimated fee.
  • Stop distance.
  • Target distance.
  • Risk/reward drawing.
  • Max daily loss policy.
  • Emergency cancel/flatten workflow.

Risk should be visible before the order is sent.

Lesson 5: Trade Copier Boundary​

Trade copier style workflows are high risk and must be validated separately from normal Chart Trader.

Teach only where enabled and verified:

  • Leader account.
  • Follower account.
  • Copy ratio.
  • Instrument mapping.
  • Account type.
  • Max exposure.
  • Disconnect behavior.
  • Partial fill behavior.
  • Audit log.

Do not treat copy trading as a beginner workflow.

Lesson 6: Server Strategy Surfaces​

Server/API strategy control should be taught as an operational feature, not as a replacement for local validation.

Teach:

  • Select the intended strategy.
  • Verify account and environment.
  • Start/stop intentionally.
  • Confirm strategy status after commands.
  • Check logs after failures.
  • Do not send server-paper or live commands through AI tools unless the platform explicitly supports that permission model.

Server controls need stricter audit logs than local chart inspection.

Lesson 7: Recovery Workflow​

Before live trading, users should rehearse recovery:

  1. Cancel working orders.
  2. Flatten or close position.
  3. Disconnect/reconnect provider.
  4. Restore workspace.
  5. Reopen chart and Chart Trader.
  6. Confirm position/order state.
  7. Export logs.
  8. Stop AI/order automation.

Completion check:

  • User can configure Hyperion Sim with realistic capital and commissions.
  • User can explain active order states and OCO sibling cancellation.
  • User can test Chart Trader brackets in simulation.
  • User can identify when trade copier or server strategy control is too risky for the current setup.
  • User can recover from disconnect, wrong workspace, or stuck order state.