Quanta Athena General FAQ

This FAQ follows the same operating narrative as the full Athena documentation set: structure-informed decisions, explicit controls and measurable live behaviour.

What is Quanta Athena?

Athena is an options-informed quantitative trading strategy for Gunbot. It combines volatility, parity and confluence logic with governed execution controls.

What is Athena trying to achieve?

Athena targets operating outcomes: structure-aware positioning, disciplined capital deployment, volatility-adaptive execution quality and transparent runtime observability.

These are strategic objectives, not guaranteed financial outcomes.

Why use options data for spot trading?

Options markets can show risk repricing and participant positioning before spot confirms direction. Athena uses that options context to inform spot execution timing and structure.

This is an information-advantage thesis, not a certainty and should be evaluated through live simulation and controlled deployment.

Does Athena support backtesting?

Athena is designed around live operation and live simulation workflows. Use simulator-driven validation and small-size staged rollout rather than relying on classic historical backtesting assumptions.

Why can Athena pause or avoid posting?

Athena can pause when freshness checks, regime constraints, capital limits, timer gates or venue rules indicate conditions are unsuitable.

How should I set trade size?

Start conservatively with TRADE_LIMIT, validate behaviour across multiple regimes, then scale incrementally once metrics confirm consistency.

Why might orders be rejected or not posted?

Typical causes include minimum notional constraints, disabled side toggles, timer gates, insufficient balances or safety controls.

Is verbose mode required?

No. VERBOSE is optional and mainly useful for diagnostics and tuning.

Can Athena run on multiple pairs?

Yes, but each pair should be treated as an independent risk unit with dedicated sizing and control validation.

What should I monitor first in production?

Start with operational health (Refresh Speed, Code Processing Time, Last API Call), then check regime/projection metrics, then review performance and capital efficiency.