Season 2 of the AI Trading Benchmark runs Claude Opus 4.7 and GPT-5.5 head-to-head across six instruments — EUR/USD, NAS100, US500, US30, USDJPY, and GBP/USD — on the same live market data, the same $1,000 fixed risk per trade, and the same $50,000 starting balance. Every analysis session, every evaluation chain, and every broker fill is logged into the public ledger.

This is GPT-5.5's ninth Season 2 trade and the third consecutive USDJPY long to stop. May 20 filled at 159.098, broker stop fill at 158.882 — done in under three minutes. May 21 filled at 159.187, broker stop fill at 159.071 after a 2h 35m hold. May 22 filled at 159.159, broker stop fill at 159.063 after 3h 25m. Three sessions, same instrument, same direction, same playbook (Tokyo/London-high breakout-retest long near the 160 intervention zone), same -1R outcome. The day's broker close on this trade: -$1,000 (SL), account at $46,588.

About reported results. Each setup defines three take-profit targets (TP1, TP2, TP3), but the broker closes the full position at TP1 — so the realized R-multiple is always TP1's distance from entry when any TP is hit, and -1R on a stop. The dollar P&L shown in this article is the actual broker close at TP1 (or stop). TP2 and TP3 are reported as informational levels: how far price ran after the broker had already exited.

Market Environment — May 22, 2026

May 22 read softer than May 21 across every macro input that drives USDJPY. The 10-year Treasury yield closed at 4.56%, below its 5-day EMA of 4.567% — the first time in the three-day USDJPY-long streak that yields were not confirming the long bias. The Dollar Index sat at 99.26, still above its 5-day EMA of 99.21 but no longer at session highs. The VIX printed 16.55 against a 5-day EMA of 17.22, a clean risk-on read. NYAD breadth flipped to +906 against a 5-day EMA of +327 — the strongest risk-on tape in the week.

On any classical USDJPY-long checklist, four of five cross-asset inputs (DXY, VIX, NYAD, no gold divergence) supported continuation. The fifth — the 10-year yield, the single most reliable USDJPY driver — did not. That asymmetry is the structural read of the day: equities and risk appetite were bullish, but the carry-trade engine (yield differential) was leaking. Gold closed at 4,512.52, below its 5-day EMA of 4,529.52, so no carry-unwind divergence warning triggered. There was no headline event inside the New York morning window — no Fed speaker, no BOJ verbal intervention, no MOF rate-check signal.

What did not change: USDJPY was still trading inside a hundred pips of the 160 intervention level, which kept the Macro Analysis Agent's confluence requirement at 6/7 instead of the standard 5/7. The Macro Agent printed 71% bullish on USD/Japan growth divergence (Eurozone PMI contraction, weak UK retail, soft Japanese CPI against firm US yields). The Trend Authority Agent printed 67% bullish on USDJPY with a "transitioning" regime classification — bullish lean, but explicitly flagged as not impulsive.

The single technical complication: the Tokyo/London high cluster at 159.138–159.163 — the same resistance band the model had attempted on May 20 and May 21 — was again the only level offering a tradeable long entry. Setups that require breaking the same resistance three sessions in a row, on a tape where the primary macro driver has rolled, are the lowest-probability category in the playbook. May 22 was that category.

Key Takeaways

What is the 10-year yield veto in USDJPY? USDJPY has the tightest yield correlation of any major FX pair — when the 10-year Treasury yield is below its 5-day EMA, the carry-trade engine driving USDJPY longs has rolled over. May 22's setup had four supportive cross-asset inputs (DXY, VIX, NYAD breadth, no gold divergence) but the 10-year yield was below the 5-day EMA. The setup checked 6 of 7 confluences without the primary driver confirming. The benchmark's filter logic flagged "no veto active" because yields weren't at 5-day extremes, but the structural read should have been a step down in conviction, not a green light.

Why 6/7 confluences requires 6/7 in practice, not "6/7 with caveats." GPT's first two evaluations returned WAIT — both flagged the breakout as not yet confirmed by a closed 5-minute candle. The third evaluation reversed to ENTER on a secondary trigger that the model itself logged as "imperfect" and "not fully confirmed." When the playbook's required confluences include a confirmation candle and that candle has not closed, the setup is 5/7, not 6/7 with an asterisk. Entering on a partial trigger is the structural failure point across the three USDJPY losses.

How does a setup near a known intervention level change the risk profile? USDJPY trading inside 100 pips of the 160 intervention level has a higher base rate of failed breakouts than the same setup at non-intervention levels. The Macro Agent recognizes this by raising the confluence requirement from 5/7 to 6/7. What it cannot do is filter out the lowest-probability category of conditional trades inside that zone. The benchmark is the test for whether AI traders can recognize a structurally low-probability setup before the playbook approves it.

What does three consecutive losses on the same setup template indicate? Two ways to read it: as bad-luck variance (small sample, same instrument, normal distribution of outcomes), or as a model failing to update the playbook when the macro layer beneath it has shifted. The signal-to-noise call is the experiment. Day 5 will be the read.