Quanta starSignal General FAQ

This FAQ follows the same operating narrative as the full starSignal documentation set: confluence-led decisions, controlled execution and measurable runtime behaviour.

What is starSignal?

starSignal is a quantitative strategy for Gunbot that combines multi-factor confluence, BEP-aware position logic and governed order execution.

What outcomes is starSignal trying to achieve?

starSignal targets operating outcomes: stronger signal quality discipline, tighter risk containment, deterministic execution behaviour and a low-touch persona-based operating workflow.

These are strategic objectives, not guaranteed financial outcomes.

Why can starSignal pause or skip trades?

Typical causes include timer gates, BEP constraints, trend protection, minimum notional rules, side toggles or order lifecycle safeguards.

What is TRADE_STYLE used for?

TRADE_STYLE maps starSignal cadence to a trading persona (scalper, dayTrader, swingTrader, positionTrader) by adjusting period behaviour. This is the main setup choice and is designed to avoid ongoing manual tuning.

What is auto-compound used for?

Auto-compound can increase trade limit using realised PnL at a configured percentage. It should be enabled only after baseline behaviour is stable.

Why might orders not post or get rejected?

Common reasons include exchange minimum constraints, insufficient balance, unsupported order-mode settings, timer restrictions or protective controls.

Is verbose mode required?

No. VERBOSE is optional and primarily useful for diagnostics.

Can starSignal run multiple pairs?

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

What should I monitor first in production?

Monitoring is optional for normal operation. If you choose to review runtime health, start with operational metrics and risk-gate behaviour.