How We Track MT5 Robot Versions | FX Trading Robot Lab

A trading robot should not be judged by one result, one screenshot, or one short test.

A robot version needs context.

It should be clear what the version is trying to test, whether it is still experimental, whether it has passed any live paper checks, and whether it is ready for a stronger testing stage.

FX Trading Robot Lab uses a version-tracking process to make robot development easier to follow.

The public site explains the process.

The member area contains the more specific version notes, weekly reports, setup materials, and research decisions.

Why Robot Version Tracking Matters

Many trading robots are presented as fixed products.

A trader sees a result, a short description, or a sales page and is expected to trust the system.

That is not how we approach robot research.

A trading robot can change over time.

A filter may be added. A weak condition may be removed. A version may be expanded, paused, replaced, or kept unchanged after a weekly review.

Version tracking helps answer important questions:

What is this robot version testing?
Is it still experimental?
Has it passed any live paper checks?
Did the latest audit support or reject the version?
What changed from the previous version?
Why was the change made?
Is the version ready for demo preparation?

Without version tracking, robot development becomes difficult to understand.

With version tracking, members can see the research path more clearly.

The Three Priority Levels

FX Trading Robot Lab classifies robot versions using only three priority levels:

Tested Logic;
Demo Candidate;
Demo Robot.

This keeps the system simple.

Each priority level has a different meaning.

Tested Logic

Tested Logic is the first research category.

A Tested Logic version may be a robot idea, a filter set, a strategy variation, or a live paper observation version.

It is not ready for demo testing yet.

A Tested Logic version may be used to answer questions such as:

Does this idea produce enough signals?
Does the logic behave correctly in live paper mode?
Does the version generate enough positive potential?
Does one condition damage the result?
Is the version too narrow?
Is the version too wide?
Should the next version be changed?

A Tested Logic version can produce a positive result.

But a positive result alone does not automatically make it a Demo Candidate.

The version still needs review, context, and confirmation.

Demo Candidate

A Demo Candidate is a stronger category.

A robot version may become a Demo Candidate only after it has already passed at least one stronger live paper test and the logic is clear enough to prepare for a possible demo-testing stage.

A Demo Candidate is still not a guaranteed profitable robot.

It is not a promise.

It means the version has moved beyond basic testing and may be prepared for independent demo testing if additional confirmation and packaging are completed.

A Demo Candidate should normally have:

a clear logic description;
stable live paper operation;
weekly audit evidence;
risk notes;
technical safety checks;
version history;
a reason for keeping or preparing the version.

This category helps separate stronger research versions from early experimental logic.

Demo Robot

A Demo Robot is a version prepared for independent member demo testing.

This is a later stage.

A Demo Robot should have clearer setup materials, version notes, and risk warnings.

Even at this stage, a Demo Robot is not a profit guarantee.

Demo testing is still a testing stage.

It allows members to observe a robot version in their own demo environment before any stronger decision is considered.

Why Weekly Audits Are Used

Weekly audits are the main control mechanism inside the research process.

A weekly audit reviews what happened during the observation period and records the decision for the next step.

A weekly audit may include:

weekly net R;
gross positive R;
gross negative R;
total trades;
TP exits;
SL exits;
time-based exits;
strongest conditions;
weakest conditions;
technical stability;
heartbeat and status checks;
safety checks;
open position checks;
version decision;
next-week plan.

The audit is not only about the final result.

A positive week may still contain weak conditions.

A negative week may still show one useful part of the logic.

A version with no trades may still provide useful information if it shows that the logic is too narrow or the market conditions were not suitable.

The weekly audit helps turn robot activity into a clear decision.

What Can Happen After an Audit?

After a weekly audit, a robot version may follow several paths.

It may remain unchanged.

This can happen when a version performs well and the next week is used for confirmation.

It may be modified.

This can happen when the audit shows that one filter, one condition, or one time period should be changed.

It may be expanded.

This can happen when the version is too narrow and does not generate enough observation data.

It may be filtered.

This can happen when the audit shows that some conditions consistently damage the result.

It may be paused or replaced.

This can happen when the version is not useful enough for continued testing.

It may move toward Demo Candidate status.

This can happen when the version passes stronger live paper checks and the research case becomes clearer.

It may later become a Demo Robot.

This is a later stage and requires additional preparation.

Why Some Details Are Reserved for Members

The public site explains the research process.

However, exact robot settings, detailed filter logic, specific version files, weekly result breakdowns, and setup guides are reserved for the member area.

This separation is intentional.

Public pages should help visitors understand the method:

how robot versions are tested;
why backtests are not enough;
why live paper observation matters;
why weekly audits are used;
why demo-first validation is safer;
why no robot result should be treated as a guarantee.

Member materials can go deeper:

robot library entries;
version-specific reports;
setup guides;
weekly audit notes;
change logs;
demo-candidate preparation;
detailed research decisions.

This keeps the public site simple and educational while preserving the value of the working research materials.

How This Helps Beginners

A beginner may not know how to judge a trading robot.

That is normal.

Many traders start by asking:

Is this robot profitable?

A better question is:

What stage is this robot version in?

A version in Tested Logic should not be treated the same as a Demo Candidate.

A Demo Candidate should not be treated the same as a Demo Robot.

A Demo Robot should still not be treated as a live-trading guarantee.

The version-tracking system helps beginners understand the difference between:

an idea being tested;
a version being observed;
a version being prepared;
a version being made available for demo testing.

This makes robot research easier to follow.

How This Supports Risk Control

Version tracking is also part of risk control.

It prevents every new idea from being treated as ready.

It creates a slower process:

test the idea;
observe the version;
audit the result;
compare versions;
make a decision;
prepare only stronger versions for the next stage.

This process does not remove risk.

But it helps avoid impulsive decisions.

A robot version must earn its next stage through evidence, not through excitement.

Related Guides

To understand the broader testing process, read the MT5 Trading Robot Testing Guide.

To understand the live observation stage, read the Forex Robot Live Paper Testing Guide.

Next Step

Public pages explain how the research process works.

The member area provides the more specific materials used to follow robot development in practice.

Inside FX Trading Robot Lab, members can follow robot version categories, weekly reports, change notes, and demo-candidate preparation materials.

The goal is not to present every robot idea as ready.

The goal is to track each version clearly, review it regularly, and move only stronger versions toward the next stage.

Risk Note

This page is for research and educational purposes only.

It does not provide financial advice, investment advice, or a recommendation to trade live funds.

Trading robots, backtests, live paper observations, weekly reports, and demo results do not guarantee future performance.

Forex and CFD trading involve significant risk.