Operator console
QT platform
A paper-first quantitative trading workspace for monitoring data, testing ideas, reviewing opportunities, and proving strategy behavior before capital is at risk.
mode: paper
service: qt.service
dashboard: :8765
live orders: disabled by default
How to use QT
- Learn the system. Start with /learn so signals, backtests, and risk gates are understandable.
- Check health. Use Monitor to verify heartbeat, data freshness, latest backtest, and runtime errors.
- Inspect opportunities. Use Intelligence and strategy detail pages before trusting a trade idea.
- Watch paper P&L. Use Portfolio P&L to confirm fills, fees, exposure, and drawdown.
- Promote slowly. Stay in paper mode until the live checklist, risk limits, API-key restrictions, and reconciliation steps are complete.
Platform capabilities
| Surface | What it does | Production use |
|---|---|---|
| Monitor | Service heartbeat, data freshness, latest backtest, strategy status, and runtime errors. | Use this first after every deploy or restart. The service must be healthy before trading decisions matter. |
| Learning Center | A cited study path for finance, statistics, risk, backtesting, and QT-specific exercises. | Keeps the operator from treating strategy output as a black box. |
| Trading Demo | A reproducible paper-only trade walkthrough using synthetic BTC data. | Safe in production because it never sends a live broker order. |
| Intelligence | Ranked funding, spread, basis, depeg, and wick candidates with edge and capacity context. | Use as an opportunity queue, then verify risk gates before acting. |
| Portfolio P&L | Per-strategy paper ledger, equity, cash, fees, drawdown, and recent trades. | A strategy should prove clean paper behavior here before live trading is considered. |
| Strategy Detail | One strategy's heartbeat, last opportunity, metrics, configured parameters, and P&L link. | Open a concrete strategy from the monitor table when strategy state files exist. |
Production readiness
Paper mode firstWebsite demo and current service paths are safe by default: they use paper execution and visible ledgers.
Risk gates visiblePosition sizing, stops, take-profit, time stop, drawdown switch, and cooldown are explicit before a fill.
Deployment isolatedQT runs from /opt/qt on port 8765; Follow remains separate.
Live trading gatedReal-money operation requires docs/live-checklist.md, trade-only API keys, caps, dry-run, and reconciliation.