Skip to main content

Technology / System engineering

Engineering architecture for quantitative trading systems

Emerald Legacy Systems separates signal information, monitoring, assisted management and automated execution. Distinct product responsibilities keep the signal framework from being mistaken for a single monolithic trading strategy.

Separate responsibilities, connected products

This is a conceptual responsibility map, not a sequence that sends every signal through every product. Platform adaptation and access concerns support the relevant implementation; documented results remain a separate evidence layer.

Information

Signal-generation logic

The multi-signal framework separates trend, high-resolution, scalp, range and synthesis roles. Signal context is information for interpretation, not an instruction to place an immediate trade.

Explore the signal library

Information

Indicator presentation

Emerald Legacy System

Emerald Legacy System presents the unified multi-signal framework on supported trading platforms. Chart presentation and signal meaning are separate from order execution.

Explore the indicator product

Monitoring

Scanner aggregation

Emerald Signal Scanner

Emerald Signal Scanner monitors configured symbols and signal modules. Its filters, signal-age context and chart-view workflow support review; monitoring is not automated strategy execution.

Explore Scanner workflows

Execution

Automated trading logic

Emerald Quant System

Emerald Quant System is the automated strategy implementation. Signal interpretation sits alongside trade execution, risk-management logic, position management and trade lifecycle management.

Explore Quant architecture

Assisted execution

Recovery and trade management

Emerald Recovery Expert

Emerald Recovery Expert is a separate, semi-automated product. The trader opens the first trade; subsequent management follows the configured recovery workflow. Recovery actions can add exposure and do not ensure recovery or profit.

Explore Recovery Expert

Implementation boundary

Platform adapters

The platform layer concerns how a product fits its host environment. Chart workflows, settings and execution constraints can differ; one platform's implementation is not a specification for another.

Access boundary

Licensing and entitlement runtime

Product and platform access is a separate concern from signal generation or trade decisions. The catalog distinguishes public-subscription products from private-investor Quant access; an access model does not describe an execution mechanism.

Evidence boundary

Performance documentation

Emerald Ledger connects documented results to a specific configuration and coverage period. This public documentation layer is separate from trading execution and does not certify other products' results.

Understand performance evidence
View the product catalog and execution roles

A multi-signal framework, not one entry rule

The published module roles describe distinct forms of signal context. Harmonizer combines Scalp Signal and Range Signal outputs; the public model does not specify weighting, voting or probability mechanics. Harmonizer SAFE is an auxiliary defensive helper, not a guarantee against loss.

Main Signal / Primary
Trend-oriented signal module within the Emerald Legacy System signal framework.
FineScalp / Primary
High-resolution tick / seconds-chart signal module within the Emerald Legacy System signal framework.
Scalp Signal / Primary
Short-horizon scalping-oriented signal module within the Emerald Legacy System signal framework.
Range Signal / Primary
Range-oriented signal module within the Emerald Legacy System signal framework.
Harmonizer / Primary
Signal-synthesis module that combines Scalp Signal and Range Signal outputs inside the Emerald signal framework.
Harmonizer SAFE / Auxiliary
Auxiliary defensive helper signal module that may be enabled alongside a preferred primary signal.

Signal information is not an immediate order

Interpretation, execution and position state

Quant's published capabilities include signal interpretation, automated trade execution, risk-management logic, position management and trade lifecycle management. An implementation must account for execution conditions and platform constraints; an indicator example alone does not describe these responsibilities.

Safeguards have limits

Exact entry conditions, risk limits, recovery rules and implementation safeguards are not specified here. Risk-management logic is a responsibility, not a promise of loss prevention. Recovery Expert's trader-first-entry workflow remains separate from Quant automation.

No proprietary formula, threshold or source code is needed to explain these boundaries. This website documents the products; it does not generate signals or execute trades.

Platform availability is not identical implementation

MT4MT5TradingViewNinjaTrader

MetaTrader chart context

For Legacy System and Scanner, the published MT4 / MT5 notes describe support for FineScalp custom high-resolution tick and seconds-chart workflows. Indicator presentation and expert-advisor trade management have different responsibilities.

TradingView and NinjaTrader context

Legacy System and Scanner can use native FineScalp high-resolution chart capability where available. MetaTrader offline/custom-chart mechanics are not implied. Product availability does not establish identical settings, interfaces or execution mechanisms.

FineScalp capability is not attributed to Recovery Expert or Quant. Detailed platform implementation documentation remains planned. Quant's public performance configuration remains Metals / XAUUSD on MT4; availability on another platform does not establish results there.

Access, observation and documented iteration

Licensing and entitlements concern access to a product on a platform, not its signal meaning or a guarantee of trading behavior. Validation protocols and enforcement details belong in platform and portal engineering documentation, not this public overview.

Scanner monitoring concerns configured signals. It is not evidence of a continuously monitored production service. The current Public Demo Reference Account supplies a Forward Performance Record for the stated Quant configuration; the website publishes static documentation, not a continuous trading feed.

Moving from a research concept toward production calls for implementation validation, evidence review and documented iteration. Production monitoring, where applicable, needs its own defined scope; no operational coverage or completed stage is inferred from a product listing.