Reporting period: Week 25
Robot: EURGBP V5 Parallel Candidate
Symbol: EURGBP
Timeframe: M5
Mode: PAPER_SIM_ONLY
Orders sent: NO
Observation type: Live paper testing and version audit
Executive Summary
EURGBP V5 Parallel Candidate completed Week 25 with a live paper result of -0.228R.
The internal weekly target for the EURGBP research track was +5R net per trading week. V5 did not reach this target.
The result was close to breakeven, which means the version was not a complete failure. However, the audit shows that the V5 filter structure was weaker than EURGBP V4 Control during the same observation period.
The main conclusion is that V5 narrowed the active logic too much. It kept selected SELL conditions, but it removed BUY + PARALLEL_HORIZONTAL, which was one of the strongest positive contributors in V4.
Weekly decision: EURGBP V5 requires review before the next testing stage.
Version Lineage: From V3 to V5
EURGBP V5 belongs to the EURGBP corridor research line.
The development path was:
EURGBP V3 Dynamic Channel
V3 was the earlier live paper dynamic channel version. It generated more frequent paper trades and tested basic BUY and SELL behaviour around channel zones.
V3 showed that simple dynamic channel logic alone was not enough. During the audit period, V3 produced a mixed result and exposed the need for more detailed classification.
EURGBP V4 Control
V4 added corridor classification, including:
- PARALLEL_HORIZONTAL
- PARALLEL_ASCENDING
- PARALLEL_DESCENDING
- EXPANDING_UP
- other unsupported or observation-only corridor types
This made it possible to evaluate performance by direction and corridor structure.
EURGBP V5 Parallel Candidate
V5 was created as a filtered candidate based on the V4 corridor logic.
The purpose of V5 was to test whether a narrower parallel-corridor version could produce a cleaner result and reach the internal weekly target of +5R.
This means V5 was part of the same research evolution that started from V3, but the direct structural base for V5 was the corridor-classified V4 version.
What Was Changed in V5
The V5 rules were intentionally narrower than V4.
V5 core rules allowed:
- SELL + PARALLEL_ASCENDING
- SELL + PARALLEL_HORIZONTAL
V5 blocked:
- BUY conditions
- EXPANDING_UP
- PARALLEL_DESCENDING
- unsupported or non-core corridor types
The purpose of this change was to test whether a focused SELL-based parallel-corridor candidate could produce a cleaner weekly result than the broader V4 control version.
The target remained the same:
+5R net per trading week
Weekly Result Summary
EURGBP V5 Parallel Candidate did not reach the internal weekly target.
The result was close to breakeven, but it was still below the required +5R net per trading week target.
| Metric | Result |
|---|---|
| Weekly target | +5.0000R |
| Actual weekly result | -0.2280R |
| Closed trades | 31 |
| Take profit exits | 10 |
| Stop loss exits | 10 |
| Max hold exits | 11 |
| Orders sent | NO |
| Mode | PAPER_SIM_ONLY |
The result confirms that V5 remained operationally stable, but the filtered structure did not produce enough positive net R to pass the weekly test.
V5 Performance Breakdown
The V5 result came from two active direction and corridor groups.
| Group | Closed trades | Net R |
|---|---|---|
| SELL + PARALLEL_ASCENDING | 26 | +2.4115R |
| SELL + PARALLEL_HORIZONTAL | 5 | -2.6395R |
The strongest V5 group was SELL + PARALLEL_ASCENDING, which finished positive.
The weakest V5 group was SELL + PARALLEL_HORIZONTAL, which finished negative and erased the positive contribution from SELL + PARALLEL_ASCENDING.
This is an important audit result because V5 was designed to test a narrower SELL-based parallel-corridor structure. The audit shows that the structure was not strong enough to reach the weekly target.
Exit Distribution
EURGBP V5 Parallel Candidate closed 31 paper trades during Week 25.
The exit distribution was:
- Take Profit: 10 trades
- Stop Loss: 10 trades
- Max Hold: 11 trades
The total R contribution by exit type was:
| Exit reason | Count | Net R |
|---|---|---|
| TP | 10 | +10.6265R |
| SL | 10 | -10.8322R |
| MAX_HOLD | 11 | -0.0223R |
This distribution shows that V5 was almost balanced between positive and negative outcomes. Take-profit trades and stop-loss trades nearly cancelled each other out, while MAX_HOLD exits were close to neutral.
Comparison With V4 Control
The comparison with EURGBP V4 Control is the most important part of this audit.
EURGBP V4 Control finished Week 25 with:
- 83 closed trades
- +11.5341R
EURGBP V5 Parallel Candidate finished Week 25 with:
- 31 closed trades
- -0.2280R
The major difference was not only the number of trades. The more important difference was which direction and corridor groups were allowed.
V4 positive groups included:
- SELL + PARALLEL_ASCENDING: +9.3575R
- BUY + PARALLEL_HORIZONTAL: +3.4252R
- SELL + PARALLEL_HORIZONTAL: +1.7625R
V5 included only:
- SELL + PARALLEL_ASCENDING: +2.4115R
- SELL + PARALLEL_HORIZONTAL: -2.6395R
This shows that V5 removed one of the strongest V4 contributors: BUY + PARALLEL_HORIZONTAL.
The V5 filter did reduce the strategy to a more focused structure, but the reduced structure did not outperform the broader V4 control version.
What Worked
The useful part of V5 was SELL + PARALLEL_ASCENDING.
This group produced:
- 26 closed trades
- +2.4115R
This confirms that SELL PARALLEL_ASCENDING remains a valid condition and should not be rejected.
However, in V5 this group was not strong enough by itself to reach the weekly target.
The result suggests that SELL PARALLEL_ASCENDING can remain part of the EURGBP research line, but it should not be treated as a complete standalone version without additional supporting conditions.
What Failed
The weakest part of V5 was SELL + PARALLEL_HORIZONTAL.
This group produced:
- 5 closed trades
- -2.6395R
This result is important because V4 showed SELL PARALLEL_HORIZONTAL as positive, while V5 showed it as negative.
This means the issue may not be the corridor group itself. The issue may be the exact entry filter, timing, smaller trade sample, or the way this condition behaved inside the narrower V5 structure.
The bigger problem was that V5 removed BUY + PARALLEL_HORIZONTAL, which was positive in V4 and helped V4 exceed the weekly target.
Why V5 Did Not Reach +5R
V5 failed to reach the weekly target for three main reasons.
First, the strategy became too narrow. By blocking BUY conditions, V5 removed BUY + PARALLEL_HORIZONTAL, which was one of the best-performing parts of V4.
Second, the remaining SELL-only structure was not strong enough. SELL + PARALLEL_ASCENDING was positive, but its result was only +2.4115R, which was below the +5R weekly target.
Third, SELL + PARALLEL_HORIZONTAL was negative in V5 and removed most of the gain from SELL + PARALLEL_ASCENDING.
The final result was therefore close to breakeven instead of strongly positive.
This does not mean that every V5 idea was wrong. It means that the V5 filter set was too restrictive and did not preserve enough of the strongest V4 behaviour.
Operational Notes
The technical operation of V5 remained stable during the observation period.
Confirmed operational points:
- the scheduled task remained active;
- Task Scheduler returned Last Result 0;
- heartbeat files updated correctly;
- status files updated correctly;
- V5 remained in PAPER_SIM_ONLY mode;
- orders_sent remained NO;
- no real orders were sent.
The V5 result was therefore a strategy result, not a technical failure.
Version Decision
Decision: UPDATE NEEDED
EURGBP V5 Parallel Candidate should not be promoted to demo testing.
Reason:
- the weekly target was not reached;
- the final result was slightly negative;
- the filtered structure underperformed V4 Control;
- BUY + PARALLEL_HORIZONTAL was removed but proved important in V4;
- SELL + PARALLEL_HORIZONTAL was negative in V5.
V5 should remain an audit reference, but it should not be treated as the next active working version.
Future Plan
The next EURGBP version should not simply continue V5 unchanged.
The Week 25 audit suggests that a future candidate should be based on V4’s strongest structure, not only on V5’s restricted SELL-only logic.
A possible future direction:
- keep V4 unchanged as the control benchmark;
- test V4 for one more live paper week;
- keep observing SELL + PARALLEL_ASCENDING;
- restore or preserve BUY + PARALLEL_HORIZONTAL as a valid candidate group;
- review SELL + PARALLEL_HORIZONTAL before allowing it in a future filtered version;
- avoid promoting V5 to demo stage.
The immediate next step is to test V4 unchanged for another week. If V4 again produces +5R or higher under clean live paper conditions, then V4 can be considered for demo-candidate preparation.
Final Conclusion
EURGBP V5 Parallel Candidate did not meet the Week 25 objective.
The version finished at -0.228R, close to breakeven but below the internal target of +5R.
The audit shows that the V5 filtering idea was too restrictive. It kept a valid positive component, SELL + PARALLEL_ASCENDING, but removed an important strong component from V4, BUY + PARALLEL_HORIZONTAL.
EURGBP V5 should not be promoted. It requires review and should remain below EURGBP V4 Control in the current version hierarchy.
Risk Note
This report is part of a live paper research process.
EURGBP V5 Parallel Candidate operated in PAPER_SIM_ONLY mode, and no real orders were sent.
Live paper results, historical observations, and internal robot research do not guarantee future performance. Forex and CFD trading involve significant risk. This report is provided for research and educational purposes only and does not constitute financial advice.
Next Version Specification — EURGBP V5.26
Series: EURGBP V5
Version: V5.26
Week: 26
Priority: Tested Logic
Purpose: Expanded trade palette test
Mode: PAPER_SIM_ONLY
Orders sent: NO
Reason For V5.26
EURGBP V5.25 finished Week 25 with -0.228R.
The result was close to breakeven, but V5.25 did not reach the internal +5R weekly target.
The Week 25 audit showed that V5.25 was too narrow. It allowed only selected SELL-based parallel corridor conditions and blocked all BUY conditions.
V5.25 active groups were:
- SELL + PARALLEL_ASCENDING: +2.4115R
- SELL + PARALLEL_HORIZONTAL: -2.6395R
The audit also showed that EURGBP V4 Control had a positive contribution from:
- BUY + PARALLEL_HORIZONTAL: +3.4252R
This group was blocked in V5.25.
Therefore, V5.26 is created to expand the V5 trade palette and test whether the V5 logic can generate enough profitable trades before negative filters are applied.
Main Research Objective
The objective of V5.26 is not to produce the cleanest possible net result immediately.
The objective is to determine whether the expanded V5 logic can generate at least:
+5R or more from profitable trades
This means the main metric for V5.26 is:
gross_positive_R >= +5R
This target is evaluated independently from the number or size of losing trades.
At this stage, losing trades are not aggressively filtered out. They are recorded and analysed later.
Why Gross Positive R Is The Main Metric
V5.26 is a potential-discovery version.
Before filtering negative trades, the system must first confirm that the logic contains enough positive trade potential.
If profitable trades cannot produce +5R or more, then filtering losses will not create a strong candidate. There must first be a positive trade palette worth improving.
After positive potential is confirmed, the next version can focus on reducing negative trades.
What Changes From V5.25
V5.25 allowed:
- SELL + PARALLEL_ASCENDING
- SELL + PARALLEL_HORIZONTAL
V5.25 blocked:
- BUY conditions
- PARALLEL_DESCENDING
- EXPANDING_UP
- unsupported or non-core corridor types
V5.26 expands the allowed trade palette.
V5.26 should allow:
- SELL + PARALLEL_ASCENDING
- SELL + PARALLEL_HORIZONTAL
- BUY + PARALLEL_HORIZONTAL
The main change is:
BUY + PARALLEL_HORIZONTAL is added back into the V5 series for Week 26 testing.
What Should Not Be Changed Yet
V5.26 should not be over-filtered.
Do not remove losing groups only because they were negative in Week 25.
Do not block all losing hours.
Do not block all SL-producing patterns.
Do not optimise the version only to improve the final net result.
At this stage, the goal is to observe the full trade palette and measure positive potential.
V5.26 Allowed Logic
Allowed entry groups:
- SELL + PARALLEL_ASCENDING
- SELL + PARALLEL_HORIZONTAL
- BUY + PARALLEL_HORIZONTAL
Blocked or non-core groups:
- BUY + PARALLEL_ASCENDING
- SELL + PARALLEL_DESCENDING
- BUY + PARALLEL_DESCENDING
- EXPANDING_UP
- EXPANDING_DOWN
- EXPANDING_BOTH
- CONTRACTING corridor types
- OTHER_UNSUPPORTED
These blocked groups may be reviewed in future versions, but they are not part of V5.26.
V5.26 Key Metrics
The Week 26 audit must calculate:
- gross_positive_R;
- gross_negative_R;
- net_R;
- positive trade count;
- negative trade count;
- total closed trades;
- TP count;
- SL count;
- MAX_HOLD count;
- result by direction and corridor type;
- result by exit reason;
- result by UTC date;
- result by UTC hour.
The main V5.26 success metric is:
gross_positive_R >= +5R
The secondary metric is whether any direction and corridor group shows a clear positive contribution.
V5.26 Decision Rules
If V5.26 produces gross_positive_R >= +5R, then the V5 series has enough positive trade potential to continue.
The next step would be to analyse losing trades and create a follow-up version, such as V5.27, with targeted negative filters.
If V5.26 does not produce gross_positive_R >= +5R, then the expanded V5 logic is still too weak. In that case, the V5 series should be expanded further or redesigned.
V5.26 Expected Output
V5.26 must write to separate output files.
It must not overwrite V5.25 files.
Expected files:
- eurgbp_parallel_week26_live_status_v5_26.csv
- eurgbp_parallel_week26_live_heartbeat_v5_26.csv
- eurgbp_parallel_week26_live_signals_v5_26.csv
- eurgbp_parallel_week26_live_open_position_v5_26.csv
- eurgbp_parallel_week26_live_closed_trades_v5_26.csv
- eurgbp_parallel_week26_v5_26_task.log
Safety Requirements
V5.26 must remain paper-only.
Required safety settings:
- PAPER_SIM_ONLY
- orders_sent = NO
- no real order execution;
- no order_send logic;
- no live account trading logic;
- no automatic real trade placement.
V5.26 is a Tested Logic version and must not be treated as a Demo Candidate or Demo Robot.
Weekly Audit Requirement
V5.26 must receive a weekly audit after Week 26.
The report should be part of the EURGBP V5 Series and should clearly state:
- version: V5.26;
- week: 26;
- priority: Tested Logic;
- what changed from V5.25;
- whether gross_positive_R reached +5R;
- what groups produced profitable trades;
- what groups produced losses;
- whether V5.27 should filter, expand, or redesign the logic.
Final V5.26 Specification
EURGBP V5.26 is an expanded trade palette test inside the EURGBP V5 Series.
It adds BUY + PARALLEL_HORIZONTAL back into the V5 logic while keeping the existing SELL-based parallel groups.
The version is not designed to hide losing trades. It is designed to reveal whether the V5 series contains enough positive trade potential to continue development.
If profitable trades reach +5R or more, then the next stage will be targeted loss filtering.