Trading mode
OFF
Scanner idle. No entries will be taken.
Safe
Account awareness
MFFU 25K
Remaining DD$1,000
Risk / trade$50
Auto size3 contracts
Auto positions1 max
Market scanner
ETF is the signal source. Future is the execution vehicle.
9:30–10:30 ET
Active position
No open trade
The first valid setup can occupy the single Auto slot.
Additional setups
Approval queue
Nothing waiting for approval.
Live ruleset
CPT execution logic
EntryETF PMH/PML breakout
StopTrailing far side of 5/12 cloud
Auto size3 contracts
Risk gate3–5% of remaining drawdown
Key levelsPDH/PDL · MTF cloud break · 34/50 cloud break
Extra entriesAlert + manual approval
Session activity
Signal log
Session replay
Test a trading day like it is live
Upload TradingView data, pick a date, then replay it bar-by-bar. CPT uses the same PMH/PML entry logic, one-position rule and 5/12 trailing stop. In Auto, the breakout enters 3 simulated micro futures contracts automatically.
Clock—
ETF price—
PMH—
PML—
Breakout—
5/12 stop—
Sim P&L—
Waiting for a CSV.
Replay uses the ETF as the signal source and reconstructs your Ripster clouds from HL2: 10m 5/12 + 34/50, 1H MTF 5/12 + 34/50, and Daily MTF 20/21 + 50/55. Load the matching futures CSV to show simulated dollar P&L. Daily MTF matching is best with 60+ prior trading sessions loaded.
Event tape
What CPT would have done
Signals, automatic entries, stop ratchets, decision checkpoints and exits appear here in order. Playback pauses when your live system would require a discretionary decision.
Start a replay to see the session behavior.
Local backtest
Import TradingView CSV
Tests the ETF signal mechanically: PMH/PML trade-through from 9:30–10:30 ET. The stop stays on the far side of the live 10-minute 5/12 cloud and ratchets tighter as that cloud moves. Key-level decisions remain discretionary.
1. Signal ETF CSV
Use SPY / QQQ / IWM chart data with extended-hours bars.
2. Matching futures CSV (optional, for $ P&L)
SPY→MES · QQQ→MNQ · IWM→M2K. Without this file CPT shows R, not fabricated dollar P&L.
Best accuracy: export 1-minute ETF + futures data with extended hours and enough history for the higher-timeframe EMAs. CPT reconstructs Ripster EMA clouds using the exact HL2 source from your settings, not Close.
Backtest rules
What CPT will test
Premarket calculation4:00–9:29 ET
New entry window9:30–10:30 ET
Breakout triggerPMH / PML trade-through
Stop10m Ripster 5/12 far side · EMA on HL2 · ratchet tighter
Unstopped positionClose at regular-session end
Profit checkpointsReplay pauses · batch backtest assumes CONTINUE
Batch resultFollows the trade through every checkpoint to final 5/12/session exit
Replay is interactive. The batch backtest assumes you press CONTINUE at each discretionary checkpoint so it can show the full mechanical path and final outcome. The ETF decides the trade and stop. Dollar P&L comes from the matching futures CSV at the same timestamps. If futures data is missing, CPT reports R only.
Results
Backtest report
Upload a TradingView CSV and run the test.
Trades0
Final win rate0%
Wins / losses0 / 0
Net P&L—
Decision alerts0
Ambiguous0
Batch backtest behavior: CONTINUE at every discretionary key-level alert, then follow the 10m 5/12 trailing stop to the final exit. Use Session Replay above when you want to choose EXIT or CONTINUE yourself.
| Date | Trigger | Side | ETF entry | Initial stop | ETF exit | Final result | R | Decision checkpoints passed | Futures fill | P&L | Final exit reason |
|---|
TradingView Strategy Tester
Production-grade backtest path
1
Convert CPT rules to Pine strategyThe strategy reads SPY/QQQ/IWM signals and can use the correlated futures chart as the execution series.
2
Run Strategy Tester / Deep BacktestingTradingView calculates historical simulated fills, trade list, win rate, drawdown and profit factor.
3
Forward-test in ObserveCompare live CPT alerts against the Pine strategy before Confirm or Auto is allowed to place orders.
TV
Signal platform
TradingView
TradingView does not need your password inside CPT. CPT receives authenticated alert webhooks from your Pine indicator/strategy.
Webhook backend not deployed
https://your-cpt-server.com/api/tradingviewCPT will keep the webhook secret server-side. Never place broker passwords or login credentials inside a TradingView alert message.
MFF
Broker / prop account
MFFU · Tradovate
Live CPT should authenticate through a secure backend and receive account/order permissions without saving your broker password in this browser.
Live API backend not connected
Account profileWill sync after API connection
Account size25K–250K auto-detect
Remaining drawdownLive risk input
Connection architecture
Credentials stay out of the app file
1You authorize the broker securely
2CPT backend stores encrypted token / API credentials
3TradingView sends signed setup events
4Risk engine validates account + 3–5%
5Auto submits 3 micro futures contracts when permitted
6Orders + account state sync back to CPT
Risk per trade
5%
Applied to remaining allowable drawdown.
Remaining DD$1,000
Max risk$50
Account simulator
Detected profile
Execution
Trade behavior
Auto contracts3 fixed micros
Manual sizingSelectable
Open Auto instruments1 at a time
Key-level no responseContinue + trail
Integrations
Connection status
TradingView webhookBackend required
MFFU / TradovateBackend required
Account metadataSimulated until connected
Use the Connections tab for the secure login architecture and TradingView setup. This local HTML file never stores your broker password.