Deployment plan · the build-out, lane by lane
loading…
Plan · progress · pace · odds from here
loading…
Book · realized vs expected (theo basis)
loading…
Strategy performance · forward tape vs replay benchmark · RT fills, commission-net
All
Live
Sim
Today · what traded, and what just happened
Accounts that traded · current session
Recent trades · newest first, all accounts
Connections · data feed health
Account arming · which accounts may fire
Pos — the account’s current position, from its own heartbeat.
Strategy — running: a strategy instance is live on this account and honouring the gate. stopped: nothing is running, so arming it has no effect. UNGATED: running with the arm gate switched off — it enters on every signal no matter what is ticked here.
Armed? — what is actually true at the strategy, as opposed to what is ticked here. YES: the instance’s own heartbeat reports it is armed, so the change has reached it and that account can take trades. PENDING: written to the database but the instance has not confirmed — normal for a few seconds after applying, but if it persists the account name does not match what NinjaTrader reports and nothing will fire. LOCAL: armed at the instance itself, from its own ARMING tab rather than from here, so it CAN trade even though nothing is ticked above — ticking and applying here takes ownership of it. no: not armed anywhere, so the gate blocks every entry.
A ticked box is a live state, not a pending action — it stays ticked because that is what “this account is armed” looks like, and unticking it is how you disarm.
Changes reach the fleet on each instance’s next arm poll. Disarming blocks new entries only — it never flattens an open position.
Strategy — running: a strategy instance is live on this account and honouring the gate. stopped: nothing is running, so arming it has no effect. UNGATED: running with the arm gate switched off — it enters on every signal no matter what is ticked here.
Armed? — what is actually true at the strategy, as opposed to what is ticked here. YES: the instance’s own heartbeat reports it is armed, so the change has reached it and that account can take trades. PENDING: written to the database but the instance has not confirmed — normal for a few seconds after applying, but if it persists the account name does not match what NinjaTrader reports and nothing will fire. LOCAL: armed at the instance itself, from its own ARMING tab rather than from here, so it CAN trade even though nothing is ticked above — ticking and applying here takes ownership of it. no: not armed anywhere, so the gate blocks every entry.
A ticked box is a live state, not a pending action — it stays ticked because that is what “this account is armed” looks like, and unticking it is how you disarm.
Changes reach the fleet on each instance’s next arm poll. Disarming blocks new entries only — it never flattens an open position.
Strategies · live status · theoretical vs actual · slippage
Markets · daily · delayed (TradingView)
Apex account state · what Apex reads (Rithmic)
Tradovate account state · registry-derived: baseline + logged P&L since true-up (Phidias / Tradeify)
Measured slippage · RT fills per instrument / account
sim fills are polite — never a slippage verdict
| Instrument | Account | Fills | Entry slip | Exit slip | RT slip | Avg spread | Last fill |
|---|
Equity curve (cumulative ticks)
Recent sessions
| Session | Instrument | Acct | Trades | W/L/T | Win% | Net ticks | Net $ | Worst MAE $ |
|---|
Safety halts