Skip to main content
Simulation sits between the Strategy Canvas and Intent History. Use it after authoring or reordering strategies, but before treating the live automation loop as production-ready. The page is vault-scoped. Select the vault first, then choose whether to run a historical backtest or a forward-looking simulation against the current strategy set.

​
Simulation Modes

Backtests are best for validating trigger thresholds, action sizing, and lane ordering against known market history. Forward simulations are better for checking a proposed strategy set before the next keeper cycle.

​
Operator Flow

  1. Open Operate → Simulation with the target vault selected.
  2. Choose backtest or forward simulation.
  3. Select the strategy set, time range, and run parameters.
  4. Run the simulation.
  5. Review the chart, metrics, generated command timeline, and per-strategy results.
  6. Save the run if it should become comparison evidence for future edits.
Simulation does not execute OMS intents or submit onchain transactions. It is a decision-support surface for strategy changes.

​
Saved Simulations

Saved simulations let teams compare strategy edits over time without rerunning every scenario. Use saved runs as review artifacts when changing thresholds, size_expr values, or lane order. They are especially useful when a strategy appears healthy in the canvas but produces too many small intents, creates oscillation, or misses a liquidity target.

​
What to Inspect

After a simulation looks correct, move to Intent History to monitor real OMS execution.

​
API Reference