Video summary

2 Entries & SL Placement

Main summary

Key takeaways

Finance

Finance-focused summary (entries & stop-loss placement)

Core framework / methodology

  • Order of operations: build analysis first, then execute based on entry models. Entry “patterns” are only meaningful after logic/criteria are defined.
  • Three entry models (used in priority order):
    1. Turtle Soup (primary)
      • Trade the stop-run inside a key level (not a lower-timeframe price pattern).
      • When price purges stops below/above the level, buy the stop-run (for longs) rather than waiting for a “perfect” micro pattern.
      • Rationale: a “black-and-white” invalidation—if the level fails, the stop-out means the idea was wrong.
    2. Confirmation entry (backup if turtle soup is missed)
      • Requires a shift in order flow on a 15-minute chart (or 5-min / 1-min if more intraday/scalping).
      • Two ways to confirm the order-flow shift:
        • Market profile shift: after taking out a low, price shifts through a high, turning retracements into buying opportunities into predetermined key levels (breakers / order blocks / gaps).
        • PDA shifting (bearish disrespected, bullish created): bearish levels are “disrespected” while bullish structures (e.g., 15-min order block/gap context) are formed—indicating order flow has switched.
      • After confirmation, enter on retracements into the relevant key structures.
    3. OTE entry (third option)
      • Essentially a turtle soup inside a key level created off the Lower High of Day (e.g., London session creating a key level; then OTE occurs in the next session).
      • Expansion → retracement → expansion
        • Miss the soup initially.
        • During the expansion phase, price retraces back into the key level generated from the lower high/day structure, then continues.

Practical example structure mentioned

  • Weekly gap / 4-hour breaker / daily rejection block each contained turtle soup scenarios (“soup inside” each level).
  • OTE example:
    • A weekly gap creates an hourly breaker
    • London low triggers a drop below a low
    • OTE entry happens on a later New York retracement back into the London-created key level
  • Confirmation examples:
    • If turtle soup is missed, wait for a 15-min order flow shift, then enter in the resulting order block / gap / breaker context.

Stop-loss placement rules (by entry model)

Turtle Soup stop-loss (author’s approach)

Stop-loss placement depends on what’s available to the left / inside the higher-timeframe structure.

  1. Intermediate-term high/low to the left (preferred)

    • If price expands beyond the range being traded (liquidity target outside the turtle-soup range), the level is likely not holding.
    • Therefore, place SL where the “range no longer is a turtle soup” invalidation occurs (near the intermediate-term liquidity point).

  2. If no intermediate-term high/low: use lower-timeframe key levels inside the higher-timeframe level

    • Example logic:
      • On a daily order block, an hourly gap inside it can define where failure is shown (e.g., if the lower-timeframe gap is closed through).
    • Stops should align with invalidation points that reflect failure of the higher-timeframe key level.

  3. Static stop-loss (when nothing is available to the left)

    • If there are no left-side reference levels, use a fixed pip distance (examples: 10/15/20/25/30 pips).
    • Discretion is tied to market volatility (a 30-pip stop could be “huge” or “not big” depending on regime).
    • Intent: the stop-out means the setup is wrong (price displacement through the level), and the trader moves to the next idea.

Confirmation entry stop-loss

After a 15-min order-flow shift, stop-loss placement choices include:

  1. Protected low that created the order-flow shift (best / primary)

    • Trust the low associated with the structural shift in order flow.
    • Works regardless of retracement type (order block, gap, breaker).

  2. Key level created off the lower high

    • If entering on a later retracement after the shift, SL can be placed using a key level formed from that lower-high context.
    • (Author mentions using a lower-timeframe key level such as a breaker to protect the stop in a bullish environment.)

  3. Tighter vs looser placement (discretionary)

    • Depending on how conservative/risky the trader is.

OTE stop-loss

  • Treated the same way as turtle soup:
    • Find a left-side intermediate-term low/high; if none, use lower-timeframe gaps/breakers inside the higher-timeframe key level to protect the stop.
  • Discretion determines how tight/wide the SL should be.

Key risk-management / behavioral recommendations

  • Turtle soup emphasizes one-and-done behavior:
    • If SL hits, you’re wrong; don’t re-enter repeatedly (avoid “one wrong idea turning into multiple losses”).
  • The method is designed to improve:
    • Risk management (clear invalidation)
    • Emotional control (binary outcome per setup)
  • Author cautions against overfocusing on execution:
    • Avoid “tiniest stop-loss / perfect precision” obsession.
    • Focus on being on the right side of the trend and using high-probability + high RR setups.

Disclosures / disclaimers

  • No explicit “not financial advice” disclaimer appears in the provided subtitles.

Extracted instruments / tickers / assets

  • No specific market tickers or ETFs are mentioned.
  • References are conceptual only, including:
    • sessions (e.g., London, New York)
    • timeframes (daily/hourly/4-hour/15-minute)
    • structures (gaps, order blocks, breakers), and PDA

Presenters / sources

  • The subtitles appear to be delivered by a single presenter (name not provided in the transcript).

Original video