The Family of Zones Every Concept Is Built From
Order Blocks, FVGs, Breakers — different names for the same underlying family of premium/discount zones.
Before you start: No prior concept needed — a good starting point for the concept category.
Part of the My Edge Official framework — refined through thousands of hours of chart study.
Every concept we sell under the "Concepts" category — Order Block, Fair Value Gap, Breaker Block, Mitigation Block — is actually just a single instance of the same broader family: the PD Array (Premium/Discount Array). This document is the overarching framework that explains why none of these concepts carries meaning on its own.
- Core Idea
- Why It Exists
- How Professionals Read It
- Practical Application
- Common Mistakes
Every individual concept we sell under the "Concepts" category — Order Block, Fair Value Gap, Breaker Block, Mitigation Block — is actually just one instance of the same broader family: a PD Array (Premium/Discount Array).
None of these zones have meaning on their own. Their value depends on: when they formed, in which session, on which timeframe, under what circumstances they formed, and what role they're currently playing.
A higher timeframe isn't automatically better — an Order Block on the 1-hour chart isn't "better" than a gap on the 5-minute chart just because it's on a higher timeframe. What matters is the circumstances of formation, not the type of zone itself.
Advanced explanation⌄
Core Idea
A PD Array has no meaning on its own. Its significance depends on: the time it formed, the session it formed in, the timeframe, its birth context, and its current role.
Why It Exists
Identity — type, timeframe, session, time of formation.
Birth context — which liquidity was taken before it formed? Was displacement present? Did a market structure shift occur? Did it form within a time anchor?
Current role — draw on liquidity, inversion, support, resistance, entry reference, or target.
Validation — has it been mitigated? Respected? Failed? Still active?
How Professionals Read It
Not all PD Arrays carry equal weight. Priority depends on timeframe, birth context, market environment, draw on liquidity, and session.
Practical Application
⚠️ A quality PD Array is never chosen because of its type. It's chosen because its context supports the current narrative. In other words: an Order Block is not "better" than a Fair Value Gap simply because it's an Order Block — it's only better if its context supports that.
On the chart you see both a 1H Order Block and a 5-minute Fair Value Gap at the same time, both at a similar price. Which do you choose? The answer isn't "the Order Block, because it's on the higher timeframe" — the answer depends on the birth context of both. If the 1H Order Block formed without displacement and without a liquidity sweep, the 5-minute FVG, which formed right after a clear sweep and MSS, actually outranks it in quality — despite the lower timeframe. Timeframe is one factor in the weighting, not the only one.
Common Mistakes
- Automatically favoring the higher timeframe. The higher timeframe does typically carry more weight, but not unconditionally — always check the birth context first.
- Ignoring the current role. A PD Array that was a target (draw on liquidity) this morning may already have become support or resistance by the afternoon — re-check the role at every significant delivery.
- Trading an already-mitigated PD Array as if it were fresh. The validation step (mitigated/respected/failed/active) isn't an administrative label — it directly determines whether the zone is even still relevant.
How to Use It
For every individual concept you purchase on this site (Order Block, FVG, Breaker Block, etc.), apply this four-step filter before you even consider it for a trade:
In practice:
- First, identity: which type, on which timeframe, in which session, when it formed.
- Then birth context: without a liquidity event or displacement before its formation, a PD Array is substantially weaker — don't discard it, but give it lower priority.
- Then current role: the same PD Array can change roles during the day (from target to support, for example) — re-check the role at every significant liquidity delivery.
- Only last, validation: has it already been mitigated or is it still active? A mitigated PD Array isn't necessarily useless, but it requires a different interpretation (see Inversion Fair Value Gap as a concrete example of a role reversal).
Don't stop here — see how this fits with the rest of the framework.
Continue to Draw on Liquidity →Frequently Asked Questions
What is a PD Array?⌄
A PD Array (Premium/Discount Array) is the overarching family that Order Blocks, FVGs, Breaker Blocks, Mitigation Blocks and similar zones all belong to — a PD Array has no meaning on its own until it's read through time, session, birth context, and current role.
How do I decide which PD Array to prioritize when several overlap?⌄
Priority isn't about type — an Order Block isn't automatically better than an FVG just because it's an Order Block; it depends on birth context, timeframe, market environment, and draw on liquidity, so a 5-minute FVG with a clean sweep can outrank a 1-hour Order Block without one.
Order Block vs FVG vs Breaker Block — how do they relate as PD Arrays?⌄
They're different shapes within the same PD Array family — the distinction that matters for trading isn't which shape it is, but its birth context, current role, and whether it still holds validation (active, mitigated, respected, or failed).
Do I need this overview if I already own the individual concept products?⌄
Yes — this is the four-step filter (identity, birth context, current role, validation) that every individual concept on the site assumes is already understood before applying its own specific assessment rules.