J3P Multi-Day Audit — EBAY · Jul 1–6, 2026

Does the J3P engine (VWAP Pull-In · Trend Trade · Backside Scalp) work inside a higher-timeframe TREND environment? · card built 2026-07-06

Environment (verified from daily bars)

Jul 1: base-high break, close 111.28 (red close, low-vol). Jul 2: trend day +2.95% close 114.84 on a 0.64 Daily-RVOL tape (dollar-breakout qualified). Jul 6: 0.63-RVOL narrow pause, close 113.605. Daily regime: TREND (up) — a fresh base breakout holding its gains, price above a rising 5-DMA the entire window. This is exactly the regime where the exit-experiment finding applies: trend plays need trend exits.

Per-session summary

SessionPlayEntryStopT1/T2 (+2σ/+4σ)Outcome (60/20/20)MA-trail alternative
7/1vwap_pull_in (long) — signal #1111.52111.13111.89 / 112.40T1 and T2 both traded through same session (high 113.57); replay page marks W +1.4R ladder*pending engine run — intraday MA-trail needs the 2-min replay; the DAILY-scale answer is already measured: TMT full-size hold = +0.56R on 100% exposure vs actual 60/20/20-style scaling = +0.56R on 5% remaining (see the EBAY playbook Management Tracking section) — same R banked, trend exposure kept only by the trail
7/1long — signal #2113.415113.00113.80 / 115.29T1 hit 7/2; T2 hit 7/2 (high 115.98) — multi-session ladder*
7/2vwap_pull_in continuation (long)per Bella Vol MA trigger-window: same-bar RVOL 1.96 @10:08, 2.27 @10:28 — re-graded qualified-Aengine ladder pendingpendingpending
7/2backside_scalp (short) — 2 signals flagged on the live overlayscreenshot-reported: "BACKSIDE short entry · R:R 4.27" markers ~13:00–13:30engine outcome pendingFLAG: counter-trend family inside a trend day — see verdict below
7/6vwap_pull_in (long) — last signal on overlayscreenshot-reported: R:R 0.39 (vwap_pull_in) — sub-1 R:R late in a pause dayengine outcome pendingpendingpending

* 7/1 rows quote the signal ladder embedded in the existing replay page's data (entries/stops/targets verbatim; target-touch dates verified against daily H/L: 7/1 H 113.57, 7/2 H 115.98). Rows marked screenshot-reported are point-in-time overlay readings from the trader's charts, not engine output — they will be replaced by the engine run.

Verdict so far (what is already answerable)

LAB material — partial audit; engine-faithful per-play outcomes and the 7/2 / 7/6 replay pages require the home-machine run (command above). Nothing here models slippage/commissions. Sources: EBAY_2026-07-01.html embedded signal data, kti daily bars (karb + Liberator 6/9 patch), trader-reported Bella Vol MA readings, TMT specimen #1 tracking.