Republished With Real Numbers: How March Opened +1.38R After the Phantom Fix

Five trades, three winners, two losses, +1.38R net on a TP1 baseline. That is the corrected scorecard for the week of March 2 to March 8, 2026, and it replaces the version we published one week ago. The original reported seven trades, a 42.9 percent win rate, and a -0.62R losing week. Two of those seven rows were phantoms: unfilled-order entries the prior pipeline treated as filled -1R losses. A methodology fix in the broker-execution log dropped both rows. The week was a 60 percent winning week, not a 42.9 percent losing one. Through Mar 9, 2026, the system has banked +8.81R YTD across 29 trades from Jan 12 inception. The simulated $100,000 account at 2 percent risk per trade sits at $117,628 on a static basis. Cumulative equity traveled from $100,000 up to $102,407 by Monday's close, dipped to $100,407 on Tuesday's stop, climbed to $102,917 by Wednesday afternoon and again to $104,767 thirty minutes later, then settled at $102,767 after Thursday's stop. Three of the five trades cleared the threshold for a standalone study: Monday's US30 primary fade at +1.20R, Wednesday's US500 buy-the-NY-pullback running to TP3 (+1.25R baseline, +3.31R full ladder), and the NAS100 breakout continuation long at +0.93R on TP1. Phantom-fill mechanics and the corrected drawdown footprint sit in the regenerated weekly drawdown report; longer-window context lives in February's monthly recap and last week's recap.

Act 1: Monday's setup, one fade and one case study

Monday March 2 produced one trade. A US30 primary fade short triggered at 16:18 UTC into a tested resistance after the macro tape cleared lean-bearish on the U.S. cash open. The trade paid +1.20R on TP1 and became the week's first standalone case study. Equity closed at $102,407.

Act 2: Tuesday's stop and Wednesday's two-case-study burst

Tuesday March 3 produced one trade. A US500 short at 15:36 UTC on a breakdown-pullback continuation read stopped at -1R as the index recaptured the breached level. Equity pulled to $100,407, leaving the week +0.20R cumulative.

Wednesday March 4 was the inflection. A US500 long at 16:19 UTC on a buy-the-NY-pullback read ran the full ladder to TP3 for +1.25R on baseline. Twenty-eight minutes later, a NAS100 long at 16:47 UTC on a breakout continuation read paid +0.93R on TP1. Wednesday closed +2.38R cumulative, equity $104,767. The week's high-water mark.

Act 3: Thursday's stop, the week settles +1.38R

Thursday March 5 produced one trade: a US500 long at 15:04 UTC on a buy-the-dip VWAP/Fib confluence read that stopped at -1R as the index lost the level intraday. Equity settled at $102,767, leaving the week +1.38R cumulative. Friday March 6 produced no qualifying setups.

Pattern of the week

Inside the corrected ledger, the structural pattern was a single instrument splitting cleanly across direction and session. US500 traded three times: once short on a breakdown-pullback (Tuesday, stop), once long to TP3 on the buy-the-NY-pullback (Wednesday, +1.25R baseline), and once long on a buy-the-dip VWAP/Fib confluence (Thursday, stop). The Wednesday winner sat in the middle of the two losers and paid more than they cost. US30 and NAS100 each traded once and won.

Why the Wednesday burst is the week

Two trades inside thirty minutes, on different instruments, each clearing its own confluence threshold, each running independently to its own TP. The Cross-Asset Agent had cleared the index pair as decoupled on the 5-minute timeframe before the NAS100 long was sized, so the Risk Agent did not apply a correlation discount. That is the cross-asset architecture working in plain sight.

Decision highlights

The Wednesday decision to take a NAS100 long 28 minutes after the US500 long had already triggered is the cleanest cross-asset judgment of the week. Both setups cleared confluence independently, and the Risk Agent sized the NAS100 entry without correlation discount because the Cross-Asset Agent had already cleared the index pair as decoupled on the 5-minute timeframe.

The Tuesday US500 short on a breakdown-pullback continuation read is the kind of trade the system will keep taking. The setup cleared confluence on its own merits and triggered on the threshold rule; the recapture invalidated the structural read after the trigger.

The Thursday US500 long at 15:04 UTC is the week's hardest decision to read in retrospect. The buy-the-dip VWAP/Fib confluence was clean at trigger; the regime softened intraday and the stop was the only exit. The macro reprice formed in the bars after the entry.

Loss worth learning from

What the system saw that was right

Both losing entries cleared the published confluence threshold at trigger. Tuesday's breakdown-pullback short was at a clean structural level on a lean-bearish DXY read; Thursday's VWAP/Fib confluence long was a textbook buy-zone on the local read. Every input was positive at the moment of trigger.

What the system got wrong

Nothing in the entries themselves. Both losses share a regime-shift sensitivity the exit logic does not address: the macro context repriced inside the trade lifecycle, and the stop was the only exit path. The system does not re-evaluate in-position trades dynamically. That is a known cost of the architecture, not a tuning signal.

What the original publication got wrong

The phantom-fill bug. Two unfilled-order rows in the broker-execution log were rolled into the recap as if they had filled at -1R apiece. The fix lives in the log-execution pipeline; the regenerated weekly drawdown report documents the same correction on the drawdown side.

From the desk

Through Mar 9, 2026, the cumulative ledger reads +8.81R YTD across 29 trades from Jan 12 inception. The same $100,000 account at 2 percent risk per trade sits at $117,628 on the static line and $118,492 on the compounded line — the spread is the cost (or benefit) of compounding through a positive-expectancy edge as winners cluster around losses.

The honest reading of this week is that we got the original wrong. Not the trades themselves, which were always five and always +1.38R net in the underlying broker data, but the recap that surfaced them. Two phantom-fill rows turned a three-of-five winning week into a published seven-trade losing week. The methodology fix in the log-execution pipeline drops both rows. We are republishing into the same canonical slot; slug, URL, and publish date are unchanged.

The architecture point holds either way. The Cross-Asset Agent did not throttle US500 between Tuesday's stop and Wednesday's TP3 winner because two trades is not a basis for instrument-level adjustment. The Risk Agent did not size down on Thursday's third US500 entry because the gate logic does not read consecutive-instrument-loss as an exclusion. A discretionary trader might have done both. The system did neither. This week the cost of that discipline was one -1R late-session stop, not a four-loss cluster. The benefit across the rolling record remains the published win rate.

What we're tuning

There is no entry-side tuning signal in either of the two losses. Both cleared the published threshold; the +1.38R net sits inside the rolling-record interquartile range. Nothing here is a parameter change.

The tuning that did happen was upstream of the recap. The phantom-fill behavior in the log-execution pipeline is now patched, and a regression test blocks unfilled-order rows from reaching the aggregator. The Wednesday two-trade burst is a feature of the cross-asset architecture, not a tunable parameter. We are not adding correlation gating on the basis of a single week.