Skip to main content

HX110 Simulation Risk And Operations

HX110 teaches what Hyperion Sim can validate, what it cannot model, and how to rehearse operational recovery without treating a Preview or Beta feature as a safety control.

Lesson 1: Select LocalPaper Explicitly​

Hyperion Sim uses LocalPaper accounts. A chart's data source does not select that account for you. The current release-candidate build rejects Broker and Server Paper order mutations while Playback is active, but that safety guard does not replace explicit LocalPaper selection.

Before every exercise:

  1. Read the visible account name and type.
  2. Confirm it is LocalPaper, not Server Paper or Broker.
  3. Confirm the provider connection and instrument.
  4. Submit only a small test order.
  5. Verify the order in Orders, the fill in Executions, and the position in Positions.

Repeat the account check after changing a connection, instrument, workspace, or restored window. See Accounts And Trading Environments.

Lesson 2: Understand The Simulator​

Hyperion Sim currently supports a simplified local execution model with immediate/latest-price market fills, incoming-tick evaluation for stop and limit orders, complete-order fills, OCO sibling cancellation, and configurable per-order/per-unit commissions.

It does not model:

  • queue position or order-book liquidity
  • partial fills
  • configurable slippage
  • provider/network latency
  • buying-power rejection
  • margin calls or liquidation
  • every exchange-specific reject or outage

Use it to find sizing, state, OCO, and workflow errors. Do not use it to predict live fill quality.

Lesson 3: Follow The Full Order Lifecycle​

Do not assume that every active order is simply Working. Provider and local workflows can report submitted, accepted, risk-accepted, working, trigger-pending, part-filled, filled, cancelled, rejected, and other states.

For one simulated Market, Limit, and Stop order:

  • record each state transition
  • change or cancel while the order is still active
  • verify the terminal state
  • verify the execution and position effect
  • confirm the UI and account model agree

If the provider account and a chart banner disagree in any later live test, the provider is authoritative.

Lesson 4: Test Every OCO Preset​

An OCO preset is not proof that protective orders exist at the provider.

For each preset on LocalPaper:

  1. Submit the entry size from Chart Trader.
  2. Confirm child stop and target sizes after the fill.
  3. Fill one child and confirm working siblings cancel.
  4. Test target allocation totals for multi-target presets.
  5. Test a one-time move-to-breakeven rule if configured.
  6. Cancel and flatten, then confirm no child remains working.

Provider routes can implement brackets differently. Re-certify the exact preset and order types before any Broker use.

Lesson 5: Do Not Invent A Universal Risk Guard​

Chart Trader and MegaDOM submit directly after their local validation. HyperionX 1.1.10 does not provide a platform-wide manual maximum-order or daily-loss guard.

Treat estimated fee, margin, leverage, stop distance, target distance, and risk/reward displays as decision support. Use provider/account risk controls for hard limits. Agent Builder's numeric risk and allowlist fields are advisory and must not be presented as enforced controls.

Lesson 6: Keep Trade Copier In Beta​

Trade Copier is Beta and is not approved for live use. Evaluate it only with LocalPaper leader and follower accounts.

During a controlled evaluation:

  • map every symbol explicitly
  • verify multiplier and copied quantity
  • test market, limit, stop, cancel, OCO, and partial-close scenarios separately
  • test disconnect/reconnect and unknown outcomes
  • compare leader/follower positions and working orders after every case
  • practice synchronization, repair, and flatten

Several displayed options are not certified enforcement boundaries, including some ATM-copy, risk-per-account, slippage, timeout, and daily-loss behaviors. Use Trade Copier Beta for the exact current limitations.

Lesson 7: Know The Automation Boundary​

The 1.1.10 Preview Local Desktop API can perform supported Hyperion Sim actions after token, permission, setting, entitlement, and confirmation checks. Newer release-enabled builds can additionally expose guarded Hyperliquid and KuCoin actions.

Internal server/marketplace strategy-control code is not a supported public automation contract. Do not teach internal endpoints, marketplace relay commands, or a live_trade entitlement value as sufficient evidence of an available live workflow. Follow Platform APIs, Local Agent Live Trading API, and Marketplace Status.

Lesson 8: Rehearse Recovery​

On a non-live account, practice:

  1. cancel working orders
  2. close or flatten the position
  3. disconnect and reconnect the provider
  4. compare HyperionX with provider-authoritative state
  5. reopen the chart and reselect LocalPaper
  6. stop strategies and AI/order automation
  7. export logs and preserve timestamps/request IDs

For an unknown submission outcome, stop retries and reconcile first. See Connection Recovery.

Completion Check​

  • You can explain every material difference between Hyperion Sim and provider execution.
  • You verify LocalPaper independently from Playback or chart data.
  • You can trace an order through active and terminal states.
  • You can prove OCO sibling cancellation and no orphaned protective order in simulation.
  • You do not rely on Trade Copier Beta or Agent Builder metadata as a loss limit.
  • You can execute and document the recovery procedure.