QUANTFLOW Trade Journal
Log every signal your scanner produces — traded or not. Data drives calibration.
📷 AI Autofill from Screenshot
Upload 1–15 screenshots from your QUANTFLOW scanner. AI reads all signal data and fills
Entry, SL, TP1, TP2, R-multiple and all scanner fields automatically. R
size risked is left for you to fill manually — set it based on your confidence (0.5R, 1R, 2R…).
🔑 AI Provider Settings
Key stored in your browser only — never
sent anywhere except the selected API.
Drop screenshot(s) here · or Ctrl+V
to paste
or click to browse · PNG, JPG · up to 15 images · paste works anywhere on this
page
🔄 Update open trades
Quickly close or update any trade that's
currently OPEN.
Fill what the scanner gave you. Fields marked * are essential for later analysis.
Everything else you can skip if the scanner didn't produce it (e.g. Pulse cards, manual-mode analyses).
Section 1 — Signal Identity
what candle you saw
Binance symbol, e.g. BTCUSDT
The timestamp of the signal candle, not now
Section 2 — Raw Signal Data
from the Intelligence Layers card
Section 3 — System Output
what the scanner recommended
Section 4 — Validation Metrics
from Step 1 & WFO cards
From TRAINED model only — not untrained
Filter level used in ML training (Loose/Relaxed/Strict)
Filter level applied during ML inference
From the candidate detail — warns of survivor bias
System Trade Plan
auto-filled from scanner — edit freely
R the system expects to risk — separate from your actual
risk
Section 5 — Your Actual Execution
fill when you enter; finish when it closes
How much R you risk: 0.5, 1, 2… = $? at current R
Auto-calculated from Entry/SL/TP2 · override after close. Signed: +2.4 win, -1.0 stop
Total fee paid for this trade in USD — deducted from P&L
Section 6 — Notes
Keep it fast: You don't need to fill every field. Required fields
(*) take 30 seconds.
The rest you copy from the scanner only if you want deeper calibration later.
The Journal tab lets you edit any entry after the fact — so you can log quickly now and update the
outcome days later when the trade closes.
| Time | Pair | TF | Dir | Rgm | AI | Win | Zone | Mgmt | ML% | EVw | PF | WFO | Taken | Outcome | R× | Plan? | Notes |
|---|
No entries yet. Log your first signal in the Log entry tab.
Log at least a few entries to unlock analytics.
How to use this journal
The core principle
Log every signal your scanner produces, whether you trade it or not. The journal's value
isn't tracking YOUR trades — it's tracking the SYSTEM's predictions against real outcomes.
You log a WAIT verdict as
HYPOTHETICAL with what would have happened; you log a TRADE you
skipped as SKIPPED — both are still data points that let you calibrate the system.
Section 1 — Signal Identity
Pair, Timeframe, Direction, Candle date/time — these identify exactly which setup you're logging.
The candle timestamp (not "now") is critical because the same coin/TF can produce multiple signals over
time.
Signal source — distinguishes Scanner (live daily scan) from Manual Analyzer (you picked a specific candle). Manual analyses often have different fill characteristics — tracking separately tells you if your discretionary picks outperform the live scanner or vice versa.
Signal source — distinguishes Scanner (live daily scan) from Manual Analyzer (you picked a specific candle). Manual analyses often have different fill characteristics — tracking separately tells you if your discretionary picks outperform the live scanner or vice versa.
Section 2 — Raw Signal Data
Copy the numbers from the 📊 6 Intelligence Layers card at the top of the scanner output.
Regime color is mandatory (GREEN/YELLOW/RED). Others optional but useful:
• Body % — how much of the candle range is body (high body = strong momentum)
• Volume × — multiple of recent average (3×+ is the minimum edge threshold)
• ADX — trend strength (25+ = trending, 40+ = strong)
• ATR ratio — volatility vs recent baseline (>1.5× = expansion)
Later we can analyze: "my wins cluster at body >60% AND vol >4×" or similar.
• Body % — how much of the candle range is body (high body = strong momentum)
• Volume × — multiple of recent average (3×+ is the minimum edge threshold)
• ADX — trend strength (25+ = trending, 40+ = strong)
• ATR ratio — volatility vs recent baseline (>1.5× = expansion)
Later we can analyze: "my wins cluster at body >60% AND vol >4×" or similar.
Section 3 — System Output (the critical one)
This is what the AI dual-candidate output tells you to do. All 6 fields mandatory:
• Winning candidate — A (newest-bucket), B (weighted all-time), Tie, or None. Copy from the 👑 WINNER badge.
• Final AI verdict — TRADE / WAIT / NO TRADE (from the winner's verdict box)
• Entry zone + SL method + Mgmt mode + TP multiplier — copy from the winning candidate's method string (e.g.
Why all mandatory? Because later analysis needs to answer: "Does Partial-NoBE actually beat Partial+BE live, like the backtest suggested?" — which requires enough samples per mgmt mode to have statistical meaning.
• Winning candidate — A (newest-bucket), B (weighted all-time), Tie, or None. Copy from the 👑 WINNER badge.
• Final AI verdict — TRADE / WAIT / NO TRADE (from the winner's verdict box)
• Entry zone + SL method + Mgmt mode + TP multiplier — copy from the winning candidate's method string (e.g.
Standard / ATR SL / Partial-NoBE / TP2.5R becomes STANDARD, ATR, PARTIAL_NOBE,
2.5).Why all mandatory? Because later analysis needs to answer: "Does Partial-NoBE actually beat Partial+BE live, like the backtest suggested?" — which requires enough samples per mgmt mode to have statistical meaning.
Section 4 — Validation Metrics (all optional but valuable)
• ML prob % — the winning candidate's ML probability (42.6% in your screenshots)
• ML label — HIGH / MEDIUM / LOW
• Backtest WR % / EVw / PF — from the 🏆 Best method card
• WFO verdict — PASS / BORDERLINE / FAIL / INSUFFICIENT from the 🔬 WFO card
• Honest PF — from the 🎯 Honest PF line if shown (excludes breakeven trades)
• Fill rate % — from the candidate detail (important for survivor bias detection)
These let you ask: "When ML says 60%+, does my actual WR match?" and "Does WFO PASS predict winners?"
• ML label — HIGH / MEDIUM / LOW
• Backtest WR % / EVw / PF — from the 🏆 Best method card
• WFO verdict — PASS / BORDERLINE / FAIL / INSUFFICIENT from the 🔬 WFO card
• Honest PF — from the 🎯 Honest PF line if shown (excludes breakeven trades)
• Fill rate % — from the candidate detail (important for survivor bias detection)
These let you ask: "When ML says 60%+, does my actual WR match?" and "Does WFO PASS predict winners?"
Section 5 — Execution (fill in 2 phases)
Phase 1 (when you log the signal):
• Did you take it? YES / NO / PAPER (tracking only, no real money)
• Risk % — how much of your account you risked (skip if NO)
• Entry / SL / TP1 / TP2 prices — copy from the trade plan card
• Outcome — set to OPEN initially
Phase 2 (when the trade closes):
• Return to the entry (edit button in Journal tab) and update:
• Outcome — WIN / LOSS / BREAKEVEN / HYPOTHETICAL
• R-multiple — signed, so +2.4 for a 2.4R winner, -1.0 for full stop, +0.5 for Partial+BE breakeven
• Followed prescribed mgmt? — YES if you traded exactly as the system said, NO if you deviated
• Exit reason — how it actually closed
• Did you take it? YES / NO / PAPER (tracking only, no real money)
• Risk % — how much of your account you risked (skip if NO)
• Entry / SL / TP1 / TP2 prices — copy from the trade plan card
• Outcome — set to OPEN initially
Phase 2 (when the trade closes):
• Return to the entry (edit button in Journal tab) and update:
• Outcome — WIN / LOSS / BREAKEVEN / HYPOTHETICAL
• R-multiple — signed, so +2.4 for a 2.4R winner, -1.0 for full stop, +0.5 for Partial+BE breakeven
• Followed prescribed mgmt? — YES if you traded exactly as the system said, NO if you deviated
• Exit reason — how it actually closed
Outcome types — pick the right one
• OPEN — trade is live, not yet closed. Default when you log.
• WIN — clean profit. TP2 hit, or trailing stop exited above entry. R = positive number (e.g. +2.0, +1.5).
• LOSS — full stop-loss hit before TP1 ever filled. R ≈ -1.0 (minus fees).
• BREAKEVEN — has TWO sub-cases depending on mgmt mode:
Partial+BE variant (TP1+BE): TP1 hit, SL moved to breakeven, then price reversed and stopped you at BE. R ≈
Partial-NoBE variant (TP1+SL): TP1 hit, BUT SL stays at original level. Price reversed past entry all the way to original SL on the remaining half. R ≈
• NOT FILLED — you logged a Standard or Sniper zone entry as OPEN, but price never retraced far enough within the 3-candle expiry window. Entry limit expired without a fill. R =
• SKIPPED — you chose NOT to enter (different from NOT_FILLED where the system couldn't fill).
• HYPOTHETICAL — AI said WAIT or NO TRADE; you watched and logged what would have happened. Use signed R.
• WIN — clean profit. TP2 hit, or trailing stop exited above entry. R = positive number (e.g. +2.0, +1.5).
• LOSS — full stop-loss hit before TP1 ever filled. R ≈ -1.0 (minus fees).
• BREAKEVEN — has TWO sub-cases depending on mgmt mode:
Partial+BE variant (TP1+BE): TP1 hit, SL moved to breakeven, then price reversed and stopped you at BE. R ≈
+0.498R (50% × 1R + 50% × 0R minus fees). Set Exit reason = TP1+BE.Partial-NoBE variant (TP1+SL): TP1 hit, BUT SL stays at original level. Price reversed past entry all the way to original SL on the remaining half. R ≈
0R
(50% × 1R + 50% × -1R = 0R, minus fees). Set Exit reason = TP1+SL.
Use the BE+SL quick-close button — it only appears when mgmt = Partial-NoBE.• NOT FILLED — you logged a Standard or Sniper zone entry as OPEN, but price never retraced far enough within the 3-candle expiry window. Entry limit expired without a fill. R =
null (no trade
happened).
This is critical to track — high NOT_FILLED rate on Standard/Sniper zones reveals survivor bias in backtest
results.• SKIPPED — you chose NOT to enter (different from NOT_FILLED where the system couldn't fill).
• HYPOTHETICAL — AI said WAIT or NO TRADE; you watched and logged what would have happened. Use signed R.
HYPOTHETICAL — tracking the ones that got away
When the AI says WAIT or NO TRADE, mark a watchlist and check what would have happened.
Log as
HYPOTHETICAL with the R-multiple you would have gotten. Over 20+ HYPOTHETICALs, you
can tell: is the AI filter saving you from bad trades (avg R < 0) or costing you good ones (avg R >
0.3)?
Followed prescribed mgmt? — catches your discretion leakage
This is the most important self-honesty field. If you deviate from the prescribed plan
(closed early because you got scared, moved SL to BE manually when system said NoBE, took
profit at 1.5R instead of holding to 2R), mark NO. Later you can compare your win rate when
you follow the plan vs when you deviate. Most traders discover their discretion
is costing them money — this field makes that visible.
Week 1 protocol
Use 0.25–0.5% risk only. Real money changes how you read signals — paper trading is not a
substitute. You are calibrating yourself against the system, not trying to make money this
week.
Goal for Week 1: 20 entries minimum (mix of TRADE / WAIT / NO TRADE), 10+ actual trades taken. This is the minimum sample size where the Analytics panel becomes useful.
Goal for Week 1: 20 entries minimum (mix of TRADE / WAIT / NO TRADE), 10+ actual trades taken. This is the minimum sample size where the Analytics panel becomes useful.
30-day review protocol
After 30 days of logging, the Analytics tab surfaces specific findings:
1. ML calibration — is 60% actually 60%?
2. Regime override check — are RED-regime TRADEs losing more than YELLOW/GREEN?
3. Zone performance — which entry (Aggressive / Standard / Sniper) has highest EV?
4. Mgmt mode live vs backtest — is Partial-NoBE outperforming Partial+BE in reality?
5. WFO predictive power — do PASS verdicts actually win more than FAIL?
6. Plan adherence impact — is your discretion helping or hurting?
7. WAIT/NO TRADE filter value — are you dodging losses or missing winners?
These produce specific, testable improvements ("cap ML LOW signals at 0.25% risk" or "skip Sniper on RED regime" or "always hold through TP1 regardless of fear") — not vague "trade better" resolutions.
1. ML calibration — is 60% actually 60%?
2. Regime override check — are RED-regime TRADEs losing more than YELLOW/GREEN?
3. Zone performance — which entry (Aggressive / Standard / Sniper) has highest EV?
4. Mgmt mode live vs backtest — is Partial-NoBE outperforming Partial+BE in reality?
5. WFO predictive power — do PASS verdicts actually win more than FAIL?
6. Plan adherence impact — is your discretion helping or hurting?
7. WAIT/NO TRADE filter value — are you dodging losses or missing winners?
These produce specific, testable improvements ("cap ML LOW signals at 0.25% risk" or "skip Sniper on RED regime" or "always hold through TP1 regardless of fear") — not vague "trade better" resolutions.
Data hygiene: The journal lives in localStorage on this
browser.
Every time you save an entry, it persists — but if you clear browser data, you lose it. Export CSV
weekly
(button in the Journal tab) and save the file. Once per month, send the CSV to Claude and ask for a
full statistical review — patterns you'll miss with eyeball analysis become obvious with proper grouping.
🗄️ Saved Snapshots
Freeze your current journal data into a named snapshot. Each snapshot is a complete
self-contained HTML file you can open in any browser at any time — full live journal with all trades, stats
and analytics intact.