NASDAQ PRODUCT BOUNDARY
NQ, MNQ and QQQ: one context, three execution surfaces.
NQ, MNQ and QQQ can share a documented NASDAQ market context, but they are not interchangeable instruments. Contract size, price increment, venue and feed must be mapped and validated separately.
Before you begin
Prerequisites
Learning objectives
- Explain: The product contract
- Explain: Instrument differences remain real
- Explain: Mapping is validation
The product contract
NASDAQ Intraday Flow uses NQ as master context and supports NQ, MNQ and QQQ. Shared context does not mean copying one instrument's price onto another.
Instrument differences remain real
NQ and MNQ are CME futures with different contract multipliers; QQQ is an exchange-traded product on another price surface. Minimum increments and data paths require explicit handling.
Mapping is validation
Each symbol is checked at the same timestamp after documented mapping and rounding.
- Use futures-aware tick rounding
- Use QQQ's own price and feed
- Complete each confirmed-to-exit lifecycle
- Block unsupported charts rather than approximate
Common mistakes
- Reading the result without the stated scope and assumptions.
- Changing the rule after seeing an outcome while still calling the data unseen evidence.
Trader Checklist
- Use futures-aware tick rounding
- Use QQQ's own price and feed
- Complete each confirmed-to-exit lifecycle
- Block unsupported charts rather than approximate
Practice exercise
Choose one of your own trading examples and write one page of rules, evidence and stopping conditions using the principles in "NQ, MNQ and QQQ: one context, three execution surfaces.".
What evidence would overturn the conclusion
The conclusion should be overturned or narrowed if a key assumption cannot be reproduced inside the supported scope, the control cannot be executed, or new out-of-sample evidence repeatedly contradicts it.