Call Mit Luca M3

Finance-focused summary (Model 3 strategy + COT/seasonality framework)

Instruments / tickers / assets mentioned

• No specific trade tickers/stocks/ETFs named in the subtitles.
• FX / currency pairs: EUR, USD, DXY (USD index), EUR/GBP, GBP/AUD vs USD (referenced conceptually).
• Futures markets: “Euro Future”, “US dollar pairs”, and “Euro Future from last Tuesday” (COT source depends on the futures contract).
• Benchmarks / indices: S&P 500 (used in a discussion of “alpha” definition).
• Data sources / indicators: COT (Commitments of Traders), seasonality, “Presidential Cycle”, Value Area High/Low, POC, “Daily Open” / Value Area concepts.
• Timeframes mentioned: 1-hour, 2-hour, 4-hour, daily, weekly, monthly, up to ~3 months.

---

Key methodology / step-by-step framework (Model 3)

(Presented as a “fixed entry model” concept with structure + multi-timeframe validation/entry rules.)

1) Core definitions (pivot gap + wick difference)

• Pivot gap / “pivot cap”: defined by two candles (one bullish + one bearish).
• Wick Difference (WD): the area between the two wicks of the pivot cap.
• Drawing/logic detail: when forming the pivot, the method uses the lower wick candle rather than always starting from the second candle to determine the relevant wick boundaries.

2) Higher-timeframe pivot “overarching” concept (risk/size condition)

• The setup requires a higher timeframe pivot gap that “works” via a one-to-one ratio concept (reversal / reaching a target level).
• Higher timeframe definition via ATR (14 days):
  • The position’s stop loss must be at least as large as ATR of the last 14 days (average range over the last 14 days).
  • Purpose: avoid trades being so small that they could hit SL within one day.

3) What “working” / invalidation means at the pivot level

• Once price touches the pivot gap:
  • It should make at least one move down to a -1 level (Z-ratio logic).
  • After that, the pivot gap is considered worked/out/invalid for further entries (no re-trading the same pivot).

4) Base timeframe selection for refinements

• Base timeframe range: from 3 days up to 3 months.
  • Examples of base gaps: 3-day, weekly, monthly, 3 months.
• Refinement search rule (go left in time):
  1. Start from the base gap timeframe.
  2. Move left/down toward lower timeframes to find a refinement wick difference:
     • Go down to 4 hours first.
     • Only go lower than 4h if no refinement is found by then.
     • If no refinement is found down to 1-hour, then the pivot is invalid (no trade allowed).
• Special constraint for a 3-month base:
  • Only search down to at most daily / 4-hour.
  • Go deeper only if needed, using the same logic.
  • Goal: avoid “thousands of refinements.”

5) Refinement validity (untouched requirement)

• The refinement wick difference must be “valid/untouched”:
  • If the pivot gap (or refinement) had already been touched in history, it is invalid.
• Cross-timeframe confirmation:
  • The same validation rules apply to refinements as to the base gap.

6) Entry-zone logic (triggering via lower timeframe confirmation)

• After the pivot-gap close:
  • Wait for the pivot loop / pivot formation candles to be fully closed (the pivot loop is not finished until both candles close).
• When price returns into the gap:
  • On entry-zone level(s), the gap becomes invalid if price crosses back such that a required condition fails.
• 15-minute confirmation:
  • After touching an entry gap, a 15-minute close determines whether the gap is gone/invalidated:
    • Touch + then close above (after touching) may invalidate that gap level.
    • Touch + then close below (after touching) keeps the entry gap valid.

7) Trade execution parameters (TP/SL + RR constraints)

• Take-profit (TP): set at the one level corresponding to the Z-ratio framework.
• Stop-loss (SL): adjusted/extended so that the SL distance targets a condition like arrive at 1.5 (per description).
• ATR + RR caution:
  • If SL would imply the trade is “too small” (or below minimum ATR), it is expanded accordingly.
• RR minimum check:
  • If the trade falls below a minimum RR threshold, the trade is off.
• Exit rules:
  • No fixed exit rules beyond early exits tied to risk-management conditions (see next section).

---

Risk management / exit rules (explicit)

Early exit for news / unpredictability

• If news is due very close to the target:
  • The trader exits before news to avoid unpredictable swings and poor realized R:R.
  • Even when the remaining distance is small (“hardly any difference”), they still close beforehand.

Early exit for higher-timeframe anti-confluence near target

• If price reacts extremely close to target but also near a higher-timeframe anti-confluence (e.g., Yi Open / higher-timeframe POC):
  • They close early when price begins moving away after a reaction (not merely at the moment of touching).

Stop-loss protection via “news near SL” slippage caution

• If price is very close to SL and news occurs:
  • Close before news to reduce the risk of SL being ignored or severe slippage during shocks.

Break-even rule

• Break-even is used only when reacting to confluence/anti-confluence logic:
  • “I only use breakeven if we are reacting to a Confluence / Anticonfluence.”
• Anti-confluences referenced as:
  • “Anticonfluences are POCs to me”
  • “Anticonfluences are Open via Daily Open” (with Value Area High/Low referenced)

---

Explicit performance / backtesting claims & thresholds

COT indicator evaluation method (separate but discussed)

COT/CT signal validation is described as:

• Positive return over the next 8 weeks
• Plus additional statistical filters:
  • Directional clarity filter (avoid ambiguity like “fell then barely recovered”).
  • Sharpe ratio threshold: at least 2:1 (“Sharpe ratio … at least 2 to 1”).
• Measurement is described as a validation framework (not necessarily the same as Model 3’s exact entry):
  • Model 3 trades align with CT signals turning green, but the “win metric” is based on 8-week forward return from the signal.

Seasonality / win-rate targets

• Seasonal window targets/filters mentioned:
  • At least 65% win rate
  • Sharpe ratio at least 1 (stated later)
• Lookback horizons:
  • Often 20 years used.
  • 5 years may be too short due to a “huge range of possibilities.”

Backtest disputes (sample size / negativity)

Participants discuss issues such as:

• Manual backtests allegedly showing negative starting balance for many assets.
• A claimed promised win rate of 70–80% (mentioned as a disputed claim).
• Sample-size estimate discussed:
  • “Ping of 28 pairs” and extrapolation giving 600+ backtests (roughly).
  • Memory estimate: ~300–500.

---

Key numbers & thresholds mentioned

• ATR length: 14 days
• Base timeframe range: 3 days to 3 months
• Refinement search limits:
  • Must find refinement down to 4h; if not found by then, go deeper.
  • Maximum depth 1h; if none found by 1h, pivot is invalid.
  • Special handling for a 3-month base to avoid excessive refinements.
• Entry confirmation timeframe: 15 minutes
• COT win evaluation:
  • 8 weeks forward
  • Sharpe ratio ≥ 2 (described as “2 to 1”)
• Seasonality windows:
  • 65% win rate threshold
  • Sharpe ratio ≥ 1
  • Prefer 20 years over 5 years

---

Disclosures / disclaimers

• No explicit “not financial advice” wording appears in the subtitles.
• The content emphasizes that perfect prediction of news is unrealistic; news is treated as gambling risk (risk framing rather than legal disclaimer).

---

Presenters / sources mentioned (at the end)

• Luca (speaks throughout the Model 3 theory and dispute context)
• Gabriel (CT/COT indicator references; indicator and usage)
• Kim (Discord/roles and moderation discussion; “Kim communicated incorrectly” mentioned in dispute)
• Kerim (mentioned in dispute about win-rate communication)
• Monti (mentioned regarding “Model 1/2” and backtesting/discretion vs fixed entry definitions)
• Elia (backtests provided earlier; mentorship group references)
• Julian (Discord/roles context and some earlier discussion references)
• David W / Digger / Flo / Gabe (mentioned briefly in chat/Discord context; one asked about Discord roles)