NQ, MNQ and QQQ: one context, three execution surfaces.

The product contract

NASDAQ Intraday Flow uses NQ as the master context. One Script supports NQ, MNQ and QQQ on standard one-minute charts.

That shared context does not make the instruments interchangeable. Their prices, minimum increments and market-data paths must be handled deliberately.

Mapping is part of validation

A master plan is checked against each supported symbol at the same point in time. Entry context, stop behavior and exits must agree after the documented price mapping and rounding rules.

• NQ and MNQ require futures-aware tick rounding.
• QQQ uses its own price surface and feed.
• Each symbol must complete a confirmed-to-exit lifecycle during the forward gate.

Chart and data limits

The launch contract supports standard one-minute charts only. Non-standard chart types and unsupported symbols are blocked rather than interpreted approximately.

Time-synchronized CME and QQQ data entitlement is an operational requirement for release testing.

Alert discipline

Alerts must be created from the current Script version and documented chart boundary. A Pine update that changes product behavior requires existing Alerts to be rebuilt.

NASDAQ Pro stays Under Review until mapping, Alert delivery and lifecycle checks have no unresolved mismatch.