Move from paper validation into live supervision, operations review, and portfolio follow-through across the signed-in execution surface.
Use this guide when you need to understand how SerenQuant moves from paper execution into live control, operational oversight, and portfolio follow-through without losing broker or realism context.
Start in /paper to validate readiness, simulated orders, and minute-tick behavior before you touch live execution.
Use /live and /operations together once a strategy is promotable and you need active supervision plus operational blockers in view.
Use portfolio, sandbox, broker routing, and execution realism as supporting surfaces that keep live decisions auditable.
These are the execution and follow-through surfaces that currently make up the signed-in control plane.
Manage watchlist scope, selected strategy, signals, intents, and execution controls for active live workflows.
Validate readiness, simulated runs, orders, fills, and minute ticks before promoting a strategy into live supervision.
Track readiness gates, reliability blockers, reconciliation, incidents, and action controls across execution operations.
Review price-first desk context, positions, activity, risk, and research handoff after execution decisions land.
Run what-if holdings and scenario trades without mutating the live trading desk state.
Manage broker profiles, route previews, and shadow-fill realism replay for execution assumptions.
Use this sequence to keep execution decisions staged, supervised, and explainable.
Use paper runs, readiness checks, and simulated order/fill review before you treat a strategy as live-ready.
Review broker routing defaults and realism replay so execution assumptions are explicit before promotion.
Move into /live only after the universe, strategy, and risk state are coherent enough to supervise actively.
Use operations for blockers and readiness, then portfolio and sandbox for follow-through and desk-level review.
The broker controls are where you make account-to-route behavior explicit before any live order flow starts.
Read the profiles, connected accounts, and route-decision counts first so you know whether the routing surface is empty, incomplete, or already active.
Use default account by mode and the accounts list together so live and paper traffic point at the intended account before you promote anything.
The preview panel shows the selected broker, fallback chain, and decision-reason JSON. Use it to verify why a route resolves the way it does.
Check recent route decisions after policy or account changes so the live path matches the preview and does not silently drift.
The realism surface is where SerenQuant turns a completed run into an auditable shadow-fill replay.
Create or select a realism profile first so the shadow run inherits the intended slippage, participation, and replay assumptions.
Only launch realism from a completed backtest that represents the strategy you plan to supervise. This keeps the shadow comparison anchored to an actual candidate.
Track created shadow runs, their status, and rerun cadence from the realism panel instead of treating replay as a one-off check.
Use the diff panel to inspect median and p95 absolute delta, per-fill differences, and the rows that explain where replay diverges from the original run.
Use these playbooks when execution posture has to move from readiness into real supervision without losing the audit trail.
Confirm paper readiness and simulated fills first, then verify broker defaults and realism posture before opening live control and operations together for the same strategy.
The live move happens with broker, realism, and operational blockers already visible instead of being discovered after activation.
Compare the route preview fallback chain with recent route-decision rows after a policy or account change so you can explain why live flow diverged from the expected path.
You either confirm that the drift is intentional and documented or catch a routing mismatch before it compounds in live trading.
Launch realism from the completed source run, inspect the shadow ledger and fill-diff panel, and use the results to decide whether the current execution assumptions still deserve production trust.
A strong strategy only graduates when replay evidence supports the live assumptions instead of contradicting them.
Do not skip paper readiness just because a backtest or research output looks strong.
Keep broker-routing defaults and realism assumptions visible before you interpret live or shadow execution outcomes.
Use operations as the escalation surface when alerts, incidents, or reliability checks stop being local to one strategy.
Treat portfolio and sandbox review as part of execution governance, not as disconnected post-trade screens.
Jump into the signed-in live control surface and review strategy, signals, and execution actions.
Review the data and routing provider workflow that influences execution defaults and recommendations.
Check the runtime and policy controls that gate execution behavior across workspaces.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issueJump to the section you need without losing your place.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issue