Elliott Wave Analytics Engine

The challenge

Elliott Wave analysis is usually subjective: two analysts label the same chart differently, and indicators that claim to find waves rarely explain why. Traders who use both TradingView and MetaTrader 5 also face two languages and two runtimes, so the same rules drift apart over time.

What we built

Our team engineered an analytics engine that recognises Elliott Wave structures by explicit, testable rules: for example, wave 2 may not fully retrace wave 1, and wave 4 may not overlap wave 1. The rules live in one machine-readable specification, from which the written rulebook and the indicator logic for TradingView and MetaTrader 5 are kept in step. The indicators are analysis-only: they never place, modify or close orders.

How it works

• A canonical, machine-readable rule specification as the single source of truth, with a resolver that generates the human-readable rulebook
• Pivots confirmed on closed candles only, so labels never repaint after the fact
• Evidence-weighted confidence capped at 100: a pattern that fails any hard structural rule scores zero, however close the Fibonacci ratios
• The same logic shipped as TradingView (Pine Script v6) libraries and indicators and as a MetaTrader 5 (MQL5) indicator, verified by automated tests and checksummed releases
• A research track for AI-assisted review: an AI may propose a short-lived plan, an independent safety compiler validates it, and execution stays confined to demo and test accounts