← Back to NitroPosted 2 Oct 2025 · Commenced 24 Sep 2026
Nitro Trades · video
My A+ Trading Strategy Explained (Works Everyday)...
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).
My A+ Trading Strategy Explained (Works Everyday)...
Key frames 4 flagged
Source: WATCH_ALONG.md Curated timeline.
02:21 · weak wick vs full body break sketch
on screen weak wick vs full body break sketch
what's said 'massive wick... this is a very weak candle'
rule it illustrates strong break
03:15 · FVG sizes
on screen FVG sizes
what's said 'decent sized... between too large and too small'
rule it illustrates FVG size
06:50 · AMZN FVGs compared
on screen AMZN FVGs compared
what's said 'this one right here... way too big'
rule it illustrates FVG size
10:10 · HOOD entry
on screen HOOD entry
what's said 'wicks right back up after respecting it'
rule it illustrates confirmation
Worked examples (2 A+ / 2 total)
| id | kind | t | instrument | date on screen | CRT TF | dir | entry mode | entry | stop | target | RR | outcome | frame |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| zIow-A1 | a_plus | 05:57–09:00 | AMZN (1m) | not shown | not shown | short | confirmation close → next open | not shown | not shown | not shown | not shown | big win, 'made my entire month' | 038_06m25s_10s.png |
| zIow-A2 | a_plus | 09:00–10:43 | HOOD (2m) | not shown | not shown | long | HOD BOS → FVG wick respect → next open | not shown | not shown | not shown | not shown | +40%; 2 runner contracts +300% next day | 058_09m25s_10s.png |
zIow-A1 · frames
zIow-A2 · 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
- A+ BOS-FVG requires clear HH/HL trend, strong full-body HOD/LOD break without big wick, decent-sized post-break FVG, and confirmation.
Entry
- FVG reaction candle closes/respects zone; enter next open; 1–5m, highest TF with FVG (usually 5m).
Stop
- Not stated in video.
Target
- Not stated in video.
Risk filters
- A+ window 09:30–11:00 (later allowed but not A+); avoid weak breaks/poor FVG size; runners may be held.
Timeframe
- 1–5m; 09:30–11:00 ET, before 11:30 tolerance.
Exceptions
- No stop or target rule in card; averaging/runners mentioned.
Pipeline outcome
My A+ Trading Strategy Explained (Works Everyday)...
Video zIow-8Ev0Rs · updated 2026-10-01
1Strategy write-up
- Main logic
- A+ BOS-FVG requires clear HH/HL trend, strong full-body HOD/LOD break without big wick, decent-sized post-break FVG, and confirmation.
- Entry
- FVG reaction candle closes/respects zone; enter next open; 1–5m, highest TF with FVG (usually 5m).
- Stop
- Not stated in video.
- Target
- Not stated in video.
- Risk filters
- A+ window 09:30–11:00 (later allowed but not A+); avoid weak breaks/poor FVG size; runners may be held.
- Timeframe
- 1–5m; 09:30–11:00 ET, before 11:30 tolerance.
- Exceptions
- No stop or target rule in card; averaging/runners mentioned.
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 |
|---|---|---|
| break_then_gap | Strong HOD/LOD break before FVG. | not yet coded |
| fvg_retest_confirmation | Confirmation close. | not yet coded |
| fvg_timeframe_select | Highest TF with FVG. | not yet coded |
| fvg_confirmation_grade | A+ confirmation concept. | not yet coded |
| fvg_range_quality | FVG size quality. | not yet coded |
| fvg_time_window | A+ morning window. | not yet coded |
Playbook summary what this video teaches
Limited data in this video's pack: no stop or target rule is stated.
- Setup (A+ BOS-FVG): clear HH/HL trend, a strong full-body HOD/LOD break without a big wick, a decent-sized post-break FVG, and confirmation.
- Entry: FVG reaction candle closes/respects the zone; enter at the next open.
- Timeframe: 1-5m, highest TF with an FVG (usually 5m).
- Window: A+ 09:30-11:00 ET (later allowed but not A+, before 11:30 tolerance).
- Avoid weak breaks and poor FVG size; runners may be held. Stop and target not stated.
Source: /workspace/nitro-setups/nitro_last15_2026-10-01/zIow-8Ev0Rs/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 or target rule is stated.
(a) Parameters and suggested defaults
| Parameter | Suggested default | Source |
|---|---|---|
break_quality | full body, no big wick | video |
tf | highest of 1-5m (usually 5m) | video |
window | 09:30-11:00 ET (A+) | video |
min_fvg_size | not specified in video, needs testing | 'decent-sized' not quantified |
stop / target | not specified in video, needs testing | not in video |
(b) Detection and entry logic
- Require HH/HL trend, then a strong full-body HOD/LOD break.
- Take the first post-break FVG above a size threshold; enter at next open after a respect candle.
- A+ only inside 09:30-11:00.
(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 |
|---|---|---|---|
break_then_gap | Strong HOD/LOD break before FVG. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_retest_confirmation | Confirmation close. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_timeframe_select | Highest TF with FVG. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_confirmation_grade | A+ confirmation concept. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_range_quality | FVG size quality. | not in Nitro code (FVG/BOS primitives in smt_strategy/ict/ are not wired) | not yet coded |
fvg_time_window | A+ morning window. | 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