Weekly Report #25 — EURJPY V1 Candidate Audit

Reporting period: Week 25
Series: EURJPY V1
Reviewed version: EURJPY V1.25
Next version: EURJPY V1.26
Priority: Tested Logic
Symbol: EURJPY
Timeframe: M5
Mode: PAPER_SIM_ONLY
Orders sent: NO
Observation type: Live paper testing and historical candidate audit

Executive Summary

EURJPY V1.25 was reviewed as part of the Week 25 research cycle.

The version was created as a narrow EURJPY corridor candidate focused on one core setup:

  • BUY + EXPANDING_UP;
  • LOWER_ZONE_BUY;
  • BUY_REJECTION_SOFT.

The technical operation of the EURJPY live paper task remained stable. The robot stayed in PAPER_SIM_ONLY mode, and no real orders were sent.

However, the Week 25 review showed that EURJPY V1.25 was too narrow as a live paper research version. It blocked most corridor types and produced limited live observation value.

The historical EURJPY audit showed that the BUY + EXPANDING_UP core still has positive potential, but it performs better when additional filters are applied.

Weekly decision: EURJPY V1.25 is replaced with EURJPY V1.26 for Week 26 testing.

EURJPY V1.26 remains a Tested Logic version. It is not a Demo Candidate and not a Demo Robot.

EURJPY V1.25 Logic

EURJPY V1.25 allowed only one core setup:

  • BUY direction;
  • EXPANDING_UP corridor type;
  • LOWER_ZONE_BUY zone;
  • BUY_REJECTION_SOFT confirmation.

All other corridor types were blocked.

This made EURJPY V1.25 a very narrow research version.

The purpose of this narrow design was to test whether EURJPY had a useful BUY impulse pattern after upward corridor expansion.

Week 25 Review

The Week 25 review showed that EURJPY V1.25 was technically safe and stable, but the logic was too restrictive.

The version remained active in live paper mode and continued to update heartbeat and status files.

Confirmed operational points:

  • the scheduled task remained active;
  • Task Scheduler returned Last Result 0;
  • heartbeat files updated correctly;
  • status files updated correctly;
  • the robot remained in PAPER_SIM_ONLY mode;
  • orders_sent remained NO;
  • no real orders were sent.

The main weakness was not technical.

The main weakness was that the active logic was too narrow and blocked most observed corridor states.

Because of that, the correct conclusion is not that the EURJPY V1 branch failed.

The correct conclusion is that EURJPY V1.25 needs to be replaced with a better filtered version based on the strongest historical candidate.

Historical Audit Findings

Historical EURJPY testing showed that the strongest V1-style setup was not a broad corridor model.

The strongest candidate remained based on:

  • BUY + EXPANDING_UP;
  • channel_range_pips between 20 and 50;
  • block entry_hour_utc = 9.

The strongest historical candidate was:

EJ_V1_RANGE_20_50_BLOCK_HOUR_9

Historical result:

Metric Result
Trades 26
Wins 19
Losses 7
Total R +16.5794R
Average R +0.6377R
Win rate 73.08%
Positive weeks 8 out of 9
Worst week -1.0375R
Best week +6.1032R

This result was stronger than using the base BUY + EXPANDING_UP setup without additional filters.

The audit showed that the EURJPY V1 branch should continue, but with a more focused filtered version.

Interpretation of the Result

The Week 25 review suggests that EURJPY behaves differently from EURGBP.

EURGBP V4 and EURGBP V5 are mainly focused on parallel corridor behaviour.

EURJPY V1 should remain a separate impulse and corridor-expansion research branch.

The stronger EURJPY signal is:

BUY impulse after EXPANDING_UP corridor behaviour

However, the setup needs additional filters to avoid weaker cases.

The historical audit identified two important improvements:

  • avoid weak channel range conditions;
  • block entry_hour_utc = 9.

Because of this, EURJPY V1.26 keeps the BUY + EXPANDING_UP core but adds range and hour filters.

Version Decision

Decision: REPLACE V1.25 WITH V1.26
Priority: Tested Logic

EURJPY V1.25 is preserved as the Week 25 version, but it is no longer the active live paper version.

EURJPY V1.26 was created for Week 26 and will continue the EURJPY V1 research line with a more focused filter structure.

The decision is based on three points:

  • V1.25 was technically stable;
  • V1.25 was too narrow for continued live paper observation;
  • historical audit results supported a filtered BUY + EXPANDING_UP version.

EURJPY V1.26 is not promoted to Demo Candidate status.

It remains a Tested Logic version.

EURJPY V1.26 Technical Specification

Series: EURJPY V1
Version: V1.26
Week: 26
Priority: Tested Logic
Mode: PAPER_SIM_ONLY
Orders sent: NO

Allowed Logic

EURJPY V1.26 allows only:

  • BUY direction;
  • EXPANDING_UP corridor type;
  • LOWER_ZONE_BUY zone;
  • BUY_REJECTION_SOFT confirmation;
  • channel_range_pips between 20 and 50;
  • entry_hour_utc is not 9.

Blocked Logic

EURJPY V1.26 blocks:

  • all SELL entries;
  • PARALLEL_HORIZONTAL;
  • PARALLEL_ASCENDING;
  • PARALLEL_DESCENDING;
  • EXPANDING_DOWN;
  • EXPANDING_BOTH;
  • CONTRACTING corridor types;
  • OTHER_UNSUPPORTED;
  • MIDDLE_ZONE_NO_TRADE;
  • channel_range_pips below 20;
  • channel_range_pips above 50;
  • entry_hour_utc = 9.

Main Week 26 Research Metric

The main metric for EURJPY V1.26 is:

gross_positive_R >= +5R

This means the first objective is to check whether the filtered EURJPY BUY impulse core can generate enough profitable trades.

Net result is still recorded, but the first question is whether the positive side of the logic is strong enough to continue development.

Week 26 Audit Metrics

The Week 26 audit should 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 UTC hour;
  • result by channel_range_pips;
  • result by exit reason;
  • technical stability;
  • safety status.

Operational Notes

EURJPY V1.26 was created as a separate script and separate scheduled task.

EURJPY V1.25 was disabled to avoid running both versions in parallel.

EURJPY V1.26 writes to separate Week 26 output files.

Confirmed V1.26 setup:

  • separate V1.26 script created;
  • separate V1.26 runner created;
  • separate V1.26 VBS wrapper created;
  • separate V1.26 Task Scheduler task created;
  • EURJPY V1.25 task disabled;
  • EURJPY V1.26 task enabled;
  • first-run check completed;
  • Last Result returned 0;
  • heartbeat file created;
  • status file created;
  • task log created;
  • no real orders were sent.

EURJPY V1.26 remains fully paper-only.

Risk Note

This report is part of a live paper research process.

EURJPY V1.25 and EURJPY V1.26 are Tested Logic versions only.

They are not Demo Candidates and not Demo Robots.

Live paper results, historical observations, and internal robot research do not guarantee future performance. Market conditions can change, and any robot version may perform differently in future weeks.

Forex and CFD trading involve significant risk.

This report is provided for research and educational purposes only and does not constitute financial advice, investment advice, or a recommendation to trade live funds.

Final Conclusion

EURJPY V1.25 was technically stable but too narrow for continued live paper observation.

The Week 25 audit showed that the EURJPY V1 branch should continue, but with a better filtered version.

EURJPY V1.26 was created for Week 26.

It keeps the BUY + EXPANDING_UP core and adds two filters:

  • channel_range_pips 20..50;
  • block entry_hour_utc = 9.

EURJPY V1.26 remains a Tested Logic version.

The purpose of Week 26 is to check whether this filtered EURJPY impulse logic can produce at least +5R gross positive R before any further development decision is made.

Research Contents