← Back to NitroPosted 28 Nov 2025 · Commenced 1 Oct 2026
Nitro Trades · video
I Failed At Trading, Until I Understood This (Price Action Secrets)
Code base used · SMT All-in-One + Roman Essentials v0.1
Target stack for Nitro CRT. Versions per /workspace/smt-python/VERSION_LOG.md.
- Code base
- SMT_AllinOne + Roman v0.1: Python power-test surface pinned 2026-09-25;
smt_strategy/allinone/, CLIsmt_strategy/run_smt_allinone_roman.py. - Order manager
- Roman Essentials Host v0.1 (pinned 2026-09-24). Param bag
essentials_params_full.json, version 2026-09-25: 294 params across 11 categories and 37 groups. - Entry plugin
- Nitro CRT plugin v1 (
nitro_crt_v1, 2026-09-24) is entry-only: it sends entry signals, and Roman Essentials/ZZ manages the trades (size, stops, TP ladder, session, max trades, trailing). - Ninja (reference)
- Full SMT Strategy V3 (
AllinOneStrategy) on PC2.
Honesty line: today's Nitro CRT backtest (run_nitro_crt_a_rebreak_bt.py, 10 stocks, clean data: −$86,953, PF 0.90, 370 trades) used a simplified Roman-style order-management stand-in (one stop, one target, 0.5% risk, max 2/day), not the full stack. It has not yet been run through the full All-in-One + Roman order manager. Source: smt-python/results/nitro_crt_weekly_clean_2026-10-01/compare_summary.json (STOCKS_COMBINED).
I Failed At Trading, Until I Understood This (Price Action Secrets)
Key frames 4 flagged
Source: WATCH_ALONG.md Curated timeline.
00:35 · CLEAR TREND vs CHOP schematic
on screen CLEAR TREND vs CHOP schematic
what's said 'every single time that price breaks a high, it gets decent follow-through'
rule it illustrates trend test 1
03:05 · failed breaks circled in chop schematic
on screen failed breaks circled in chop schematic
what's said 'what do I expect to happen on the fifth time around? another reversal'
rule it illustrates chop
06:15 · PLTR short FVG pullback
on screen PLTR short FVG pullback
what's said 'rejection, rejection, rejection'
rule it illustrates trend trade
09:55 · NVDA chop
on screen NVDA chop
what's said 'massive red followed by massive green'
rule it illustrates skip
Worked examples (2 A+ / 4 total)
| id | kind | t | instrument | date on screen | CRT TF | dir | entry mode | entry | stop | target | RR | outcome | frame |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| YNk5-A1 | a_plus | 05:42–08:04 | PLTR (options) | not shown | not shown | short | FVG pullback after low-of-day break (second break) | not shown | not shown | not shown | not shown | +76% | 030_06m15s_10s.png |
| YNk5-A2 | a_plus | 08:04–09:35 | AMD | not shown | not shown | long | FVG pullback respected after clean breakout | not shown | not shown | not shown | not shown | clean move (amount not stated) | 048_08m33s_scene.png |
| YNk5-N1 | no_trade | 09:35–11:37 | NVDA | not shown | not shown | not shown | not shown | not shown | not shown | not shown | skipped — failed breakouts + red/green alternation | 059_09m55s_10s.png | |
| YNk5-N2 | no_trade | 11:37–13:24 | not stated | not shown | not shown | not shown | not shown | not shown | not shown | not shown | skipped — uptrend but 3 failed breakouts |
YNk5-A1 · frames
YNk5-A2 · frames
YNk5-N1 · frames
Summary bullets 7
(en-orig deep-card captions; timestamps are video mm:ss; “not stated” is retained where the card gives no rule.)
Main logic
- Day-selection overlay for BOS-FVG: clear trend means breaks hold with follow-through and pullbacks make HL/LH; chop means repeated failed breaks and alternating large candles.
Entry
- With-trend FVG pullback; wait for second break when first lacks follow-through.
Stop
- Not stated in video.
Target
- Not stated in video.
Risk filters
- Decide in first 30–60m; skip chop day entirely; align 1–5m; full sizing only on perfect clear-trend day.
Timeframe
- 1–5m agreement; trend/chop verdict first 30–60m.
Exceptions
- Contains no stop/target/RR rule; mainly a filter card.
Pipeline outcome
I Failed At Trading, Until I Understood This (Price Action Secrets)
Video YNk5L_ivMcs · updated 2026-10-01
1Strategy write-up
- Main logic
- Day-selection overlay for BOS-FVG: clear trend means breaks hold with follow-through and pullbacks make HL/LH; chop means repeated failed breaks and alternating large candles.
- Entry
- With-trend FVG pullback; wait for second break when first lacks follow-through.
- Stop
- Not stated in video.
- Target
- Not stated in video.
- Risk filters
- Decide in first 30–60m; skip chop day entirely; align 1–5m; full sizing only on perfect clear-trend day.
- Timeframe
- 1–5m agreement; trend/chop verdict first 30–60m.
- Exceptions
- Contains no stop/target/RR rule; mainly a filter card.
2Already in All-in-One
- allinone_v4/levels.py::detect_levels (FVG/OB/swing levels)
- smt_strategy/ict/fvg.py and fvg_entries.py (FVG primitives)
- playbooks/runner.py::_collect_signals + combined.py::match_combined_entries (preset FVG candidates)
- allinone_v4/engine.py::_resolve_levels and ::_exit_scan (exits)
3New features
| Feature | Notes | Status |
|---|---|---|
| trend_chop_filter | Clear trend vs chop day classifier. | not yet coded |
| fvg_retest_confirmation | With-trend FVG pullback. | not yet coded |
| fvg_second_break | Wait for second break after failure. | not yet coded |
| break_then_gap | BOS-FVG ordering. | not yet coded |
| trend_followthrough_filter | Breaks must hold and pullbacks HL/LH. | not yet coded |
Playbook summary what this video teaches
Limited data in this video's pack: no stop, target or RR rule; this is mainly a day-selection filter card for BOS-FVG.
- Purpose: day-selection overlay for BOS-FVG, not a standalone entry model.
- Clear trend = breaks hold with follow-through and pullbacks make HL/LH. Chop = repeated failed breaks and alternating large candles.
- Decide trend vs chop in the first 30-60 minutes; skip chop days entirely.
- Entry: with-trend FVG pullback; wait for a second break when the first lacks follow-through.
- Align 1-5m; full size only on a perfect clear-trend day. Stop and target not stated.
Source: /workspace/nitro-setups/nitro_last15_2026-10-01/YNk5L_ivMcs/outcome.json (+ BULLETS.md / DEEP_CARD.md in the same pack)
Code model notes how the ideas map to code
Limited data in this video's pack: no stop, target or RR rule; this is mainly a day-selection filter card for BOS-FVG.
(a) Parameters and suggested defaults
| Parameter | Suggested default | Source |
|---|---|---|
verdict_window_min | 30-60 | video |
tf_alignment | 1-5m | video |
second_break | wait for it after a failed first break | video |
chop_definition | not specified in video, needs testing | described, not quantified |
stop / target | not specified in video, needs testing | not in video |
(b) Detection and entry logic
- Classify the day after 30-60 min: follow-through + HL/LH = trend; failed breaks + alternating big candles = chop.
- On trend days only, allow with-trend FVG pullback entries; require a second break if the first failed.
(c) Already coded in our Nitro CRT implementation
- The Nitro CRT runner and plugin contain no BOS / FVG / opening-range logic.
- Reusable primitives exist elsewhere but are NOT wired to Nitro: smt_strategy/ict/fvg.py::detect_fvgs, ict/fvg_entries.py::generate_fvg_entry_signals, ict/bos.py::detect_bos, allinone_v4/levels.py::detect_levels.
- Plugin nitro_crt_v1: python/signal_contract.py::build_signal only formats an entry signal (trigger_price, stop_hint, target_hint); ninja/NitroCRT_Entry_v1.cs is a stub (EmitOnly=true, session + RequireHtfBias knobs, no C1/C2 detector). Roman Essentials/ZZ is the order manager.
(d) Still to build (from outcome.json)
| Feature | Note | vs current code | Status |
|---|---|---|---|
trend_chop_filter | Clear trend vs chop day classifier. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_retest_confirmation | With-trend FVG pullback. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_second_break | Wait for second break after failure. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
break_then_gap | BOS-FVG ordering. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
trend_followthrough_filter | Breaks must hold and pullbacks HL/LH. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
Code checked: /workspace/nitro-setups/backtests/run_nitro_crt_a_rebreak_bt.py, /workspace/smt-python/entry_plugins/nitro_crt_v1/ (read only), backtests/sweep_2026-09-29/sweep_core.py. Statuses unchanged from outcome.json.
DSG /dev · Top Traders · training / second-gate only