EURUSD Short Runs to TP3 on a TRENDING Read for +1.82R Full Potential
SkyAnalyst AI journal entry: EURUSD Short on May 13, 2026 closed +1.82R on TP3. Full workspace view, decision log, and AI reasoning, unedited.
Before the trade, meet the system.
SkyAnalyst is not one AI trader. It is four specialist agents — each with its own data pipeline, each maintaining state between evaluations, and each required to agree before a position is sized. They don’t chat in prose. They write structured messages to a shared state object that each reads on every evaluation cycle. That’s what makes the system auditable — and it’s what this case study will show, step by step, on a specific setup the trend agent almost passed on.
The macro setup the morning gave us
May 13 produced one of the cleanest dollar-strong tapes of the month. EURUSD was the cleanest expression on the short side.
Yields confirmed dollar strength
The US ten-year carried over its bullish posture from the prior session, the DXY was firm above its five-day EMA, and the Macro Agent flagged lean_bear on EURUSD at 61 percent. The dollar bloc was set up for follow-through, not reversal. The 60m EMA stack on EURUSD had been bearish-stacked for hours.
VWAP + Fibonacci confluence at the entry
EURUSD opened the New York session bounced off the morning low and was approaching the prior day's VWAP at roughly 1.17089. The 38.2 percent Fibonacci retracement of the morning's range sat in the same cluster. When the first 5m attempt to reclaim that level produced a wick rejection and a candle close back below, every condition the Trend Agent looks for had cleared. See our recent GBPUSD short for the same VWAP-rejection pattern in cable.
Why TRENDING at 82 percent matters
TRENDING is the cleanest regime classification. It requires the 5m, 15m, 60m, and daily timeframes to align in the same direction with no conflicting momentum. The Trend Agent only produces 80-plus confidence scores when that alignment is present and the entry trigger is unambiguous. Both were the case here. The Risk Agent sized at 1.0 percent equity given the TRENDING tag.
The pattern we were trading
This was a textbook example of what professional traders: a VWAP-Fibonacci rejection fade. The setup combines two value-reference levels (the session VWAP and a 38.2 percent Fibonacci retracement) and treats the rejection at the cluster as the entry trigger when momentum confirms.
Why VWAP and Fib together
VWAP is a session value reference: a price most participants accept as fair across the day. Fibonacci retracements are structural levels traders watch independently. When the two coincide, the cluster is unusually heavy with both algorithmic and discretionary orders. A failure at that cluster on a candle close becomes a meaningful signal because two independent communities of traders are both reading the same line as resistance.
TRENDING regime sizing
The Risk Agent's TRENDING tag mapped to 1.0 percent equity sizing. The Trend Agent's 82 percent confidence reflected unambiguous alignment across timeframes. Both inputs combined produced a position that could take meaningful drawdown without exhausting risk if the read had been wrong. It was not, but the sizing is what makes the system willing to hold for TP2 and TP3 rather than booking at TP1 on every cleanly-aligned read.
What "rejection fade" means at the agent level
The Trend Agent does not enter on the test of the level. It waits for the rejection. A test that holds (price wicks the level and closes back through) is information, not a trigger. The trigger is the candle close back below the level on confirming momentum. On May 13, EURUSD produced exactly that sequence at 14:23 UTC.
Why TP3 stays untracked in some setups
TP3 is the system's extended target. It is reached on roughly one in eight setups in our internal data. The May 13 EURUSD was one of those eight. We do not size positions assuming TP3 will hit. The Risk Agent sets TP3 as a marker for "this is where the move ends if the macro stays perfectly aligned for the full session". When that happens, the chart confirms the macro for an unusually long window. May 13 produced that window.
Why the realized R is still TP1's R
Even on a TP3 day, the broker closes 100 percent of the position at TP1. The realized +0.85R (TP1) on this trade is what we log to the running tally. The +1.82R (TP3) is what the move actually produced on the chart. We publish both because both are honest, but only one funds the next position.
Pattern catalogue
We trade nine setups across forex and indices: NY AM continuation, NY AM session pullback, London continuation, opening-drive rejection, VWAP reclaim, range-extreme fade, breakout-retest, Asian range break, and structural failure. Each is gated by its own confluence rules. The Trend Agent does not pick a favorite. Different days produce different setups, and the system is dynamic, not dogmatic. It doesn't favor any single strategy.
Decision log
At 14:23 UTC on May 13, the GPT-5.5 Trend Agent issued the entry decision in a single trigger event. The recorded decision log shows ENTER without intermediate WAIT evaluations: the macro alignment was already in place from the prior session carry-forward, and the chart trigger (a 5m candle close back below the 1.17089 VWAP/Fib cluster) fired on the first eligible bar. The Macro Agent had lean_bear at 61 percent locked. The Cross-Asset Agent confirmed DXY supportive of the short direction. The Risk Agent computed entry 1.17085 (post-rejection close), stop 1.17225 (above the 1.17089 cluster plus 11 pip buffer), TP1 1.16966 (0.85R prior support extension), TP2 1.16885 (1.43R structural target), TP3 1.16830 (1.82R extended target). Final confidence: 82 percent. Decision: ENTER short at 1.0 percent equity under the TRENDING regime tag.
On a $100k account at 2.0% risk per trade.
Each trade risks +$2,000 (1R). The system's actual scale-out behavior may differ, see disclaimer.
| Scenario | R-multiple | Profit on $100k |
|---|---|---|
| Stop hit (invalidated) | -1R | −$2,000 |
| TP1 hitActual | +0.85R | +$1,700 |
| TP2 hit | +1.43R | +$2,860 |
| TP3 hit (max potential) | +1.82R | +$3,640 |
All six agents combined.
What this trade taught us about clean reads
A TRENDING regime at 82 percent confidence is rare. When it appears, the system can size into the full base risk because the alignment quality is high. The May 13 EURUSD short produced a TP3 hit, the cleanest possible result on the cleanest possible read. That is not a coincidence.
Regime quality predicts outcome distribution
Our internal data shows TRENDING regime trades have a higher TP2 and TP3 hit rate than TRANSITIONING trades. The reason is mechanical: TRENDING means every timeframe is in agreement, which means the move has fewer counter-trend stalls and reversals. The trade can carry into the next session without the lower-timeframe noise that ends most TRANSITIONING trades at TP1. The May 13 EURUSD short rode that quality into a TP3 hit.
The realized R does not change with regime quality
What does change is the gap between realized and full-potential R. On a TRENDING TP3 hit, the gap is large (in this case 0.97R between the +0.85R booked at TP1 and the +1.82R reached at TP3). On a TRANSITIONING TP1 hit, the realized and full-potential R are identical. The running track record only counts realized R, so a TP3 day still books TP1's R. See our May 19 US30 short for a tight-stop TRANSITIONING case where the gap was smaller.
Why we do not size up on high-confidence reads
We do not scale into positions on TRENDING reads. The Risk Agent's position scalar tops out at 1.0x of base risk. Higher confidence does not authorize larger size. The reason is that confidence inflation is a real risk in any system that combines model outputs into a single score. If we let confidence drive size, the worst miscalibration produces the worst loss. Holding sizing constant at the regime cap protects against that failure mode.
What we changed in our notes after this trade
The May 13 EURUSD short was clean enough that no methodology changes were warranted. One process note:
TP3-hit trades go in the rare-event log
Trades that reach TP3 are roughly one in eight of our setups in internal data. We are starting a separate log of TP3 hits so we can analyze what they have in common (regime, time-of-day, instrument, setup type) and whether the conditions producing them are predictable in advance. The May 13 EURUSD is the first entry in that log.
Why we are not announcing GPT-5.5 separately
This trade ran on GPT-5.5 a few days before the formal launch of the current AI Trader lineup. The system architecture has always treated model identity as an executor attribute, not as the basis of a marketing claim. The case-study reader will see "GPT-5.5" on the agents panel above. That is the level of attribution we intend: factual, not promotional.
One number you do not see in the journal
The trade had its deepest drawdown above the entry line at roughly 1.17090 on a brief 15m reclaim attempt about two hours in. The reclaim failed within the same 15m bar. Most TP3 hits do produce at least one retest attempt at the entry line, and this one was no exception. The setup held because the 1.17089 VWAP/Fib cluster acted as resistance on the retest exactly as it did on the entry rejection.
At a Glance
What this teaches about AI-driven trading
How does GPT-5.5 produce an 82 percent confidence read?
The Trend Agent's confidence score is a weighted aggregation across timeframes (5m, 15m, 60m, daily) with extra weight on the alignment quality. An 82 percent reading requires every timeframe to point in the same direction with confirming momentum on each. The model identity matters less than the input feature set, which is standardized across model executors. Both Claude and GPT versions of the Trend Agent reach 80-plus scores on the same kind of unambiguous setup.
Why use VWAP and Fibonacci together as confluence references?
VWAP is a session value reference reflecting where participants have transacted across the day. Fibonacci retracements are structural levels traders watch independently. When the two coincide on a single candle, the cluster carries orders from two independent participant groups (algorithmic VWAP-mean-reversion traders and discretionary Fib watchers). A failure at the cluster on a candle close is heavier-signal than a failure at either level alone.
What does a TRENDING regime tag actually mean in practice?
TRENDING is the Trend Agent's classification when every timeframe (5m through daily) is aligned in the same direction with no conflicting momentum. The position scalar maps to 1.0x base risk, the maximum the Risk Agent will allow. TRENDING reads typically produce higher TP2 and TP3 hit rates than TRANSITIONING reads because the move has fewer counter-trend stalls. On May 13 EURUSD, the alignment held for the full twenty-four hour holding period.
When does a EURUSD short get vetoed by the Macro Agent?
When yields turn (US ten-year crosses below its five-day EMA) or when the DXY breaks down from the dollar-bull regime. On May 13, the carry-forward yield read and the firm DXY both pointed dollar-strong, which is a green light for euro shorts. The veto would fire if yields reversed within the holding period; the Macro Agent runs alongside the open position and can flag mid-trade regime changes.
Run your markets with SkyAnalyst
Seven-day free trial. No credit card. Full access to the Trend Agent, Macro Agent, and six-factor confluence scoring.
Trading involves substantial risk of loss. Past performance is not indicative of future results. The analysis shown was produced by an AI model operating on SkyAnalyst’s live trading infrastructure; it is shared for educational and research purposes only and is not financial advice. About reported results. Every AI Trader publishes three take-profit targets (TP1, TP2, TP3) per trade. The broker closes 100% of the position at TP1, so two distinct R-multiples appear in this article. The hero R-multiple is the full-potential R: where the market actually traveled (the highest take-profit hit, or the stop loss) before the setup was invalidated or exhausted. The realized R, shown on the TP1 row of the simulated returns panel, is TP1’s R (or -1R on a stop out). The realized R is what we log to our running track record. Both numbers are honest. Showing both is what lets readers see the full arc of the move and the conservative ledger entry it produced. Simulated returns in this article are calculated against a hypothetical $100,000 account at 2% risk per trade (1R = $2,000). These are educational reference figures and do not reflect any specific account or broker execution. Your actual result depends on your position size, your risk parameters, and live market conditions.
From the SkyAnalyst Journal
US500 Long Waits for the Conditional Reclaim Before Buying the Dip
GPT-5.5 refused four times before entering US500 long at 7487.2. The Trend Agent required a reclaim of the opening-range breakdown zone, not the VWAP touch. TP1 booked +1.15R.
Eleven stops, one tape: the week structure refused to confirm
Eleven losses, nine R given back, a peak-to-trough drawdown of 10.81 percent and a longest losing streak of four. The honest portfolio view: what each stop taught us, and what the curve says about a week the structure refused to confirm.
May 18-24, 2026: A Seven-Eleven Week That Closed -2.82R Across Claude and GPT
Eighteen trades, seven winners, eleven losers, -2.82R net at TP1 baseline. Claude opened Monday with two early wins, GPT carried the index side mid-week, and a Friday cluster netted both sides back toward flat without crossing it.