AEGIS · LIVE / MAINNET · TECHNICAL NOTE · 25 AUG 2026

Evidence Boundary for a Spot Trading Engine

Evidence status.

DEPLOYMENT: LIVE / VERIFIED
PERFORMANCE: NOT YET PUBLICLY VALIDATED
BACKTEST: SEPARATE EVIDENCE SET

Live operation proves operational capability, not profitability or causal contribution from any signal component. No win rate, return or drawdown is published because independently reproducible sanitized performance records are not yet public.

Abstract

AEGIS is deployed on Binance mainnet with real capital. The deployment is supported by production exchange configuration and retained exchange-side order, fill, commission, execution and closure records. Its deterministic path combines five-minute market candles, regime and ATR calculations, and live order-book imbalance. A local LLM may approve or reject a fully formed candidate but cannot alter entry, stop-loss or take-profit values. Live execution is long-only. Historical replay cannot reproduce order flow and therefore forces an OFI direction when evaluating numeric entry/exit logic. Deployment, live performance and backtest are treated as separate evidence sets.

1 · Architecture OBSERVED

The current configuration names BTCUSDT, ETHUSDT, SOLUSDT and BNBUSDT; consumes 5-minute candles with a 150-candle lookback; and schedules the decision cycle hourly. The 5-minute timeframe is the data resolution; the hourly scheduler is the current decision-cycle cadence, with each cycle evaluating the latest 150 candles. Signal construction is numeric and synchronous. Regime, ATR and order-flow determine whether a card exists. The live executor rejects non-LONG cards on the spot path.

Risk sizing budgets 2% of available balance at the stop distance. A 5% current-balance daily loss cap trips a persistent circuit breaker. Reconciliation, stale-position checks and closure recording run around the execution cycle.

2 · LLM boundary OBSERVED

The optional local-model layer receives an already locked candidate. It may approve or reject and provide narrative rationale; it is instructed not to change numeric trade parameters. Signal generation remains available when the narrative enrichment layer fails. Contribution has not yet been isolated through controlled ablation. Its presence therefore does not establish causal performance contribution.

3 · Historical simulation BACKTEST

The scheduled replay fetches 5,000 recent 5-minute candles per configured symbol. Historical best-bid/ask depth changes are unavailable, so the real OFI gate cannot be replayed. The engine instead evaluates forced bullish and forced bearish OFI scenarios. These are conditional numeric simulations, not end-to-end replicas of live operation.

4 · Live deployment LIVE / MAINNET

AEGIS has executed real-capital Binance mainnet orders. Retained records include exchange order identifiers, realized entry fills, commissions, partial-fill-aware quantities, protected exits and closure journals. This verifies deployment and operational execution. It does not establish profitability or equivalence with backtest results.

Current journal P&L is not published as a strategy-performance result: entry commissions are recorded from fills, while some exit commissions remain estimated rather than independently retrieved from exchange trade history, and not every closure has a fully comparable fill path. Account-balance growth is not used as a substitute because deposits and withdrawals would contaminate it.

5 · Limitations

6 · Reproducibility / Evidence

ItemAudited value
MarketBinance Spot
SymbolsBTCUSDT, ETHUSDT, SOLUSDT, BNBUSDT
Timeframe / history5m / 5,000 recent candles
Window150 candles
Exit modelSL or TP1; stop first on same-candle ambiguity
CostsFees, spread and slippage not modeled
Result statusNOT YET VALIDATED for public performance reporting

Source boundary: `ordis_prime/core/aegis_engine/` as audited on 2026-08-25. Private code, credentials and operational account data are intentionally not published.