Technology

One pipeline,
end to end.

Every signal travels the same auditable path: real market data in, central research, risk validation, paper benchmarking, one master signal, per-client delivery, local broker validation, execution, and a reported outcome. Nothing is generated on the client and nothing is executed by the admin.

01
Central market data

The Admin EA and Admin Broker APIs are the only data sources. Live quotes, OHLC and full instrument metadata land in one central store with freshness tracking. Without a verified admin source the engine stops — it never falls back to client data or public feeds.

02
AI research

Multi-agent research over the central store: trend, momentum, volatility and structure agents score each enabled symbol. Failures are recorded as failures — never silently swallowed.

03
Strategy engine

Registered strategies combine the research into candidate opportunities per symbol and timeframe, with per-strategy performance tracked from real paper outcomes.

04
Risk engine

A 25-point pre-trade checklist validates action, stops, volume, exposure and policy before a candidate can become a signal. Risk states ride on the signal itself.

05
Central paper trading

Every signal is benchmarked on the central paper engine first — reference price, simulated entry, spread, slippage and P&L are recorded and auditable.

06
Master signal

One canonical signal per symbol and opportunity: entry zone, SL, TP ladder, TTL, confidence, strategy and the adaptive spread and buffer policies.

07
Per-client delivery

The master signal is delivered to each client independently — MT5 EA, API broker or the mobile app — with an idempotent per-account ledger. One client's rejection never cancels another's delivery.

08
Client-side validation

Your connection resolves the canonical symbol at your broker, then checks market hours, session, live spread against the policy, the execution zone, volume, margin, broker stop distances and duplicate state.

09
Execution + reporting

The order is placed only at your broker, and the exact outcome — fill, slippage, rejection reason — flows back to the central ledger as an audited event.

Fail-closed by design

No verified admin data means no master signals — the engine reports CENTRAL_SOURCE_UNAVAILABLE instead of guessing.

Audited end to end

Every hop — data ingest, AI decision, publication, delivery, execution, rejection — writes an audit event with actor, symbol and correlation.

Separation enforced

Admin connections are data-only server-side. Client connections are execution-only. The API rejects any attempt to cross the line.