Skip to model research
Systematic Trading ModelsSpecification / Evaluation / Release

MQL5 Signals: model audit questions

Account-copying infrastructure. A documentation-based note, not a measured performance ranking.

Original editorial revision: 9 October 2026. Expanded edition: 14 October 2026.

Research design and arithmetic, not model recommendations. Classification scores are not monetary returns; a registered artifact and a passing software test are not independent strategy validation.

Account-copying infrastructure

Separate the publisher model from the subscriber copying policy. Broker, volume, currency and synchronization settings can alter the executable account path even when the source model identity is unchanged.

Evidence still needed

Request immutable model identity, training and label periods, feature availability, transformation fit scope, action and exit policies, complete trial registry and independent evaluation. A purchased signal record additionally needs its original instructions, amendments and execution assumptions. Ask what the documented tool does before comparing it with a proprietary model.

Assessment boundary

No paid-account test, complete trade population or independent execution comparison was supplied for this entry. Current terms, regional eligibility and the exact purchased offer require direct confirmation. No rating, rank or consumer-review count is asserted.

Source documents

Documentation establishes the stated mechanism, not tested trading performance. Checked 9 October 2026; a later version can differ.

Copying adds a receiving-account policy

The publisher strategy and subscriber copying settings are separate decision systems. Broker, currency, volume and synchronization can alter the receiving path without changing the original signal text. This public-document note is not a paid test, measured reliability study or score of financial benefit. Save the source version with the exact claim it supports. A familiar platform brand does not identify the source population or positive label of a trading classifier. The publication has no proprietary run artifact to inspect for this resource. Where a feature or model is undisclosed, the appropriate outcome is an explicit evidence request, not a made-up numerical model grade.

The model-card question for this resource

A publisher model record cannot be substituted for subscriber quantities and executions. Preserve entitlement, selected settings and exception history alongside the underlying model identity. Identify code or rule version, input availability, transformations, labels, action threshold and any permitted intervention. If no learner is involved, document the rule-selection history instead of pretending that no fitting implies no selection. If a model is trained, request its exact reserved evaluation and allowed fit scope. The site's cards are authored and not attributed to this platform. Their complete forms demonstrate questions without filling a vendor's missing evidence or claiming that an authentic deployment used those teaching assumptions.

One source instruction, two receiving policies

A fictional publisher issues one teaching instruction while two anonymous receivers use different quantity and synchronization settings. This does not supply actual MQL5 executions, but it exposes why the source record is not automatically either receiver's account record. The subscriber help is relevant to the copying mechanism. A genuine comparison must identify the actual broker environment, selected policy and completed receiving actions. A publisher's attractive account percentage cannot be relabelled a subscriber percentage without quantities, timing and compatible accounting. These are evidence requests, not allegations about a measured platform defect.

In a model card, separate publisher identity, copying configuration and the subscriber's risk and intervention policy. If settings change mid-period, preserve their effective dates and the resulting version boundary. Pending, failed or partial actions need their own history rather than being erased from a returns-only summary. The site's authored classifier has no account copy connection and cannot certify synchronization behavior. No paid account was opened or monitored for this profile. Product mechanics can be documented honestly while real model-selection and subscriber execution evidence remain outstanding.

What would support a stronger assessment

Supply the exact selected product, lawful data entitlement, complete eligible source population, candidate history and independently scoped research evidence. Operational claims need the actual deployed artifact and subscriber route. Financial comparisons need compatible accounting and observed receiving execution. None was collected for this profile, so no paid-account return, latency estimate, review count or rank is added. The resource can still be useful in its documented role. A later source should strengthen only the claim it actually answers rather than silently upgrade every related paragraph into a verified endorsement.

Primary references and scope

Source review: 14 October 2026. Official mechanism descriptions are not this desk's paid-account test, independently captured fills or vendor-return audit.