LiquidityLab
Learning Paths

Framework Mapping Learning Path

Framework Mapping Learning Path: SMC, ICT, Wyckoff, Elliott Wave, Harmonic Patterns, and Chan Theory as translation layers, not signals.

Framework Mapping is the part of LiquidityLab that helps you understand how different trading frameworks describe the same market structure.

It is not a way to collect confirmation signals.

The rule is simple:

one market, one structure, many languages.

SMC, ICT, Wyckoff, Elliott Wave, harmonic patterns, and Chan Theory can all be useful as vocabulary. None of them should replace the Market Structure OS.

For the full layer map, start with LiquidityLab Market Structure OS. This page focuses only on the Framework Mapping layer.

Before you start

Do not begin with framework vocabulary.

Start with the neutral structure layer first:

  1. LiquidityLab Market Structure OS
  2. Market Structure Basics
  3. Trading Range Structure
  4. Trend Reversal Framework
  5. Price Action Reading Basics
  6. Four Market Scenarios Framework

If those pages are unclear, framework labels will make the chart feel smarter without making your reading more stable.

What Framework Mapping means

Framework Mapping means translating the same neutral structure into a framework's vocabulary.

For example, one visible structure might be described as:

  • a range with a failed breakout in price-action language
  • a liquidity sweep in SMC / ICT language
  • a spring-like test in Wyckoff language
  • a possible corrective structure in Elliott Wave language
  • a review zone in harmonic-pattern language

These descriptions are not votes.

They are translations.

1. SMC / ICT vocabulary

Start here if you are seeing terms such as liquidity, order block, FVG, BOS, MSS, inducement, or PD Array.

Boundary:

SMC / ICT terms are vocabulary for describing structure. They are not evidence that price must move to a specific place.

2. Wyckoff

Use Wyckoff when you want to think about range behavior, supply, demand, effort, and result.

Boundary:

Wyckoff labels are observation tools. They do not prove hidden intent or a fixed phase roadmap.

3. Elliott Wave

Use Elliott Wave when you want a textbook language for wave counts, driving structures, and corrective structures.

Boundary:

A wave count is a hypothesis. It is not a forecast.

4. Harmonic patterns

Use harmonic-pattern language when you want to understand ratio-based structure classification.

Boundary:

Ratios classify geometry. They do not create entries, stops, targets, or expected reversals.

5. Chan Theory

Use Chan Theory when you want to understand a Chinese structure-analysis tradition built around inclusion, fractals, strokes, segments, central pivots, and recursive levels.

Boundary:

Chan Theory buy-point and sell-point terms are framework vocabulary on this site, not trading instructions.

How to compare frameworks safely

When comparing frameworks, use this sequence:

  1. Write the neutral structure first.
  2. Identify the market state: trend, pullback, range, or transition.
  3. Mark visible highs, lows, ranges, and failed breaks.
  4. Then translate the same structure into one framework language.
  5. Stop before turning the translation into a trade decision.

Do not ask:

Do SMC, Wyckoff, and Elliott all agree, so can I trade?

Ask:

What does each framework call the same visible structure, and where do their definitions differ?

Common mistakes

Mistake 1: treating framework agreement as confirmation

If three frameworks describe the same area, that does not make the outcome more certain.

It only means three vocabularies can describe the same structure.

Mistake 2: mixing definitions

An order block, a Wyckoff spring, a harmonic review zone, and a Chan central pivot are not interchangeable.

They may overlap visually, but they come from different definition systems.

Mistake 3: learning advanced vocabulary before basic structure

If you cannot clearly say whether price is trending, pulling back, ranging, or transitioning, advanced terms will usually add noise.

Mistake 4: using a framework to avoid uncertainty

Framework labels can make uncertainty feel smaller.

But a label is not evidence.

Practice routine

Pick one historical chart and write:

Neutral structure:
Framework translation:
What the translation adds:
What the translation does not prove:
What would invalidate this reading:

Keep the translation short. The goal is clarity, not vocabulary density.

Summary

Framework Mapping helps you understand how different systems describe market structure.

Use it to translate, compare, and learn.

Do not use it to vote, predict, or execute.

Next, practice the same rule inside the AI Structure Workbench Beginner Manual: write the neutral structure first, then translate it only as a reference layer.

On this page