Backtesting & Monitoring
Backtesting is one of the core safeguards in the Orien product model.
Why Backtesting Matters
Orien is explicitly designed to move away from fragile prompt-only trading. Backtesting is part of that philosophy:
- validate strategy behavior before live deployment
- inspect strategy traces over historical periods
- compare factor combinations and parameter choices
- reduce reliance on intuition alone
How Backtest Mode Works
In backtest mode, the agent:
- loads historical K-line data
- replays the strategy one cycle at a time
- applies the same runtime concepts used in deployment
- records actions, trades, positions, and summary metrics
What You Can Inspect
The platform can surface:
- K-line charts with trade markers
- PnL evolution
- win rate and drawdown
- Sharpe-like performance indicators
- cycle-by-cycle reasoning traces
Monitoring Pipeline Agents
Monitoring is not only for backtests. For pipeline agents, the same mindset continues in production:
- inspect cycle output
- track trade execution
- observe position drift
- review runtime status
- identify risk rejections and abnormal behavior
This is part of the value of the second layer of the architecture. Autonomous agents should not be opaque.