Operator View

Private simulation workspace

Purpose-built views for operations, simulation audit, account control and historical replay.

Protected Edge Simulation Mode Audit Trail

Operations

Start here when you want to monitor the live system

Use this view to check whether the worker is active, which targets are enabled and what the last automatic decision was.

What To Do Here

Use this view for day-to-day monitoring

  1. Check `Trading cycle status` to see if the worker is processing targets.
  2. Open `Trading cycle targets` to confirm what market/account pairs are active.
  3. Use `Live cycle` only when you want one manual snapshot or one manual run.

Good Sign

The system looks healthy when

  • `workerState` is `processed` instead of error.
  • `lastRunId` and `processedCount` keep changing over time.
  • Your enabled target appears in the targets table.

Automation

Trading cycle status

Loading trading cycle worker status...

Target State Last snapshot Last decision Last run Processed

Targets

Trading cycle targets

Loading enabled cycle targets...

Name Market Account Strategy Mode Triggers
Create cycle target

Targets are stored in the database and picked up by the worker.

Live Cycle

Exchange snapshot and run-once

Loading exchange adapters...

Simulations

Read what the strategy decided and why

Filter stored runs, open one result and inspect the decision, execution outcome and account snapshots side by side.

What To Do Here

Use this view to understand decisions

  1. Filter the run list by symbol, strategy or action.
  2. Click one row in the table.
  3. Read the right-hand panel to see why the system chose `Buy`, `Sell` or `Hold`.

Read It Like This

The most useful questions here are

  • Why did the strategy hold instead of trading?
  • Was a trade really executed or only evaluated?
  • What changed in the account before and after the run?
Visible Runs 0 Current filtered scope
Buy Runs 0 Actions marked as BUY
Executed 0 Runs with execution
Average Edge 0.00% Across current list

History

Simulation history

Loading simulation history...

Time Account Symbol Strategy Action Edge Executed Exec Price

Run Details

Select a run from history

Click a table row to inspect decision, execution and account snapshots.

Accounts & Strategy

Configure the account and rules the system uses

This is where you create simulation accounts, review analytics and adjust strategy settings before running automation or replay.

What To Do Here

Use this view before you automate anything

  1. Create or select a simulation account.
  2. Make sure the account has sensible capital and context.
  3. Pick or edit the strategy configuration the worker should use.

Why It Matters

Operations depends on this setup

  • No account means the worker has nothing real to simulate on.
  • Bad thresholds mean lots of noisy or useless decisions.
  • Presets are shortcuts, but strategy configs define the real behavior.

Accounts

Virtual account context

Loading accounts...

Analytics

Account analytics

Select an account to view analytics.

No equity curve is available yet.

Replay & Data

Use this as the lab for historical checks

Prepare a local dataset, run historical backtests and use manual or batch simulations when you want to test ideas away from live automation.

What To Do Here

Use this view for experiments, not live monitoring

  1. Prepare a local dataset for replay.
  2. Run a historical backtest on that dataset.
  3. Use manual or batch simulation when you want controlled experiments.

Keep In Mind

This is your lab bench

  • Live API data helps with operations.
  • Replay data helps with repeatable testing.
  • Custom JSON import is advanced and optional.

Historical Data

Local datasets and replay

Loading historical datasets...

Dataset Symbol Timeframe Candles First Last
Import custom candle dataset

Use this only when you want to paste your own candle JSON into a local replay dataset.

Replay

Historical backtest

Backtest will replay candles into persisted simulation runs.

Historical backtest summary will appear here after the first run.