Weekly Report #26 — EURGBP V4.26 Control

EURGBP V4.26 ISO Week 26 Live Paper Report

Reporting period: ISO Week 26
ISO week window: 2026-06-22 00:00 UTC to 2026-06-28 23:59 UTC
Active market observation window: 2026-06-22 00:00 UTC to 2026-06-26 23:59 UTC
Robot: EURGBP V4 Control
Version label: EURGBP V4.26
Symbol: EURGBP
Timeframe: M5
Mode: PAPER_SIM_ONLY
Orders sent: NO
Observation type: Live paper testing
Weekly research target: +5R net per week
Final result: -8.8269R
Target status: FAIL

Executive Summary

EURGBP V4.26 failed the weekly research target during ISO Week 26.

The robot closed 40 paper trades and finished the week at -8.8269R. The required research target was +5R net per week, so the weekly target was not achieved.

This week is important because EURGBP V4 had previously produced a strong initial live paper observation result. Week 26 therefore acted as a confirmation week. The confirmation failed.

The result does not remove EURGBP V4 from the research programme. It shows that the V4 Control structure is not yet stable enough for demo deployment without further logic testing.

The Week 26 result became the basis for a new Week 27 test idea: EURGBP V4.1.27 with an opposite second-slot structure.

EURGBP V4.26 weekly target versus actual result showing minus 8.8269R against a plus 5R target.
EURGBP V4.26 weekly target versus actual result during ISO Week 26.

Weekly Result Summary

The final Week 26 result was negative.

Weekly target: +5.0000R
Actual result: -8.8269R
Difference from target: -13.8269R
Closed paper trades: 40
Gross positive R: +12.2831R
Gross negative R: -21.1101R
Mode: PAPER_SIM_ONLY
Orders sent: NO

The gross positive side shows that the robot was still able to produce profitable paper trades during the week. However, the negative side was significantly larger, and the week closed below both the weekly target and the 0R break-even level.

The result confirms that Week 26 was not a temporary small deviation. It was a material failed confirmation week.

Net R by Direction and Corridor Type

EURGBP V4.26 net R by direction and corridor type showing which corridor groups contributed to the negative weekly result.
EURGBP V4.26 net R by direction and corridor type during ISO Week 26.

The direction and corridor breakdown is used to identify where the V4 Control logic became weak during the week.

In Week 25, several corridor groups supported the positive result. In Week 26, the same control structure did not repeat that behaviour. This is the key reason why the week is treated as a failed confirmation rather than a successful continuation.

This chart is important because it shows that the weekly result was not only a final number. It also provides diagnostic information for the next version.

Realised Balance Path During ISO Week 26

The chart below shows how the realised balance developed during ISO Week 26.

The starting value is normalised to 0R. Entry markers show when paper trades were opened, and exit markers show when realised R was added to the running balance.

This chart helps show the full weekly path, including the maximum realised peak and the realised drawdown during the week.

EURGBP V4.26 realised balance path showing 40 closed paper trades and a final result of minus 8.8269R.
EURGBP V4.26 realised balance path during ISO Week 26.

Balance path summary:

Start of week: 0R
Final result: -8.8269R
Maximum realised peak: +1.2923R
Maximum realised drawdown: -11.0317R
Closed paper trades: 40

The balance path shows that the robot briefly moved into positive territory, but the weekly structure did not hold. The realised drawdown reached -11.0317R from the running peak, which is too deep for a candidate intended to move toward demo testing.

This makes the chart one of the most important parts of the report. It shows not only the final loss, but also the shape of the loss during the week.

Exit Distribution

EURGBP V4.26 exit reason distribution showing 10 TP, 17 SL and 13 MAX HOLD exits from 40 closed paper trades.
EURGBP V4.26 exit reason distribution during ISO Week 26, showing 10 TP exits, 17 SL exits and 13 MAX_HOLD exits from 40 closed paper trades.

Exit reason summary:

TP: 10
SL: 17
MAX_HOLD: 13
Closed paper trades: 40

The exit distribution was weaker than required for a stable weekly candidate.

The number of SL exits was higher than the number of TP exits. MAX_HOLD exits also remained significant. This means that the robot was not simply losing because of one isolated event. The weakness appeared across the exit structure.

A stronger candidate would normally need either a better TP-to-SL balance, a reduced SL count, or better filtering around the conditions that produced the negative trades.

Methodology Clarification

This report uses strict ISO-week reporting.

The reporting period is ISO Week 26, from 2026-06-22 00:00 UTC to 2026-06-28 23:59 UTC. The active market observation window for EURGBP ended on 2026-06-26, because Forex trading is normally closed during the weekend.

From Week 26 onward, weekly reports should use a standard ISO-week structure wherever possible. This makes weekly comparisons clearer and reduces confusion between initial observation windows and recurring weekly reports.

All results in this report are paper-only. No real orders were sent.

Safety Status

EURGBP V4.26 remained in paper simulation mode during the reporting period.

Mode: PAPER_SIM_ONLY
Orders sent: NO
Real-money execution: Disabled
Purpose: Research observation only

This report should not be interpreted as financial advice or a recommendation to trade. The result is part of a research record for evaluating robot behaviour under live paper conditions.

Week 26 Conclusion

EURGBP V4.26 failed the weekly research target during ISO Week 26.

The robot closed 40 paper trades and finished the week at -8.8269R, compared with the required weekly target of +5R. The exit distribution also showed a weaker structure than the previous observation window, with 10 TP exits, 17 SL exits, and 13 MAX_HOLD exits.

This result is important because EURGBP V4 had previously produced a strong initial live paper observation result. Week 26 therefore acted as a confirmation week. The confirmation failed.

However, this does not mean that the EURGBP V4 Control candidate is abandoned. It means that the robot is not yet ready for demo deployment without additional logic testing. The Week 26 failure provided useful information about where the current structure becomes vulnerable.

Based on this result, a new Week 27 test version was prepared: EURGBP V4.1.27. The new logic keeps the EURGBP V4 corridor foundation but adds an opposite second-slot structure for live paper testing.

The purpose of the next version is not to hide the failed week, but to test whether the weak Week 26 behaviour can be improved by allowing a controlled second paper position only in the opposite direction.

The failed week is part of the research record, not something removed from the system.

The new logic starts from 2026-06-29 and will be tracked in the next weekly report.

Read the new logic description here:

EURGBP V4.1.27 Opposite Second Slot Logic — Week 27 Test


Navigation

Back to EURGBP V4 Research Archive

Back to Research Archive

Back to Robot Library

Research Contents