Defining a Chart Contract for Market Structure Analysis

Hello. This course is intentionally procedural: the aim is not to add more SMC vocabulary, but to make every label reproducible in replay and defensible in real time. Before deciding whether a move is a BOS, CHoCH, or merely internal noise, you need to ensure that “the chart” means one fixed, auditable object.

By the end of this lesson, you will have a chart contract: a short specification that fixes the instrument, feed, candle construction, time basis, session treatment, timeframe roles, and the exact meanings of external, internal, and protected structure. It is the control document for the rest of the course.

---

Why a chart contract comes before structure

Two traders can look at “XAUUSD 1H” and honestly disagree about a swing without either being careless. They may be viewing:

• different price sources: a broker CFD, a futures contract, a spot quote, or a composite feed;
• different daily rollovers and 4-hour candle boundaries;
• different weekend or maintenance-break handling;
• different regular-session settings;
• different chart time zones.

Those differences can change the high or low that forms a pivot, whether a candle closes beyond a level, and whether a supposed displacement bar exists at all. This matters especially for the exact confusion you want to eliminate: a “CHoCH” that appears clear on one feed may not even take the relevant swing on another.

A chart contract does not make a method profitable. Its purpose is narrower and essential: it prevents you from changing the evidence after seeing the outcome.

Use one contract per tradable market-feed combination. For example, an analysis on a broker’s XAUUSD CFD is not automatically interchangeable with an analysis of gold futures. Similarly, BTCUSDT perpetual data from one exchange is not the same dataset as a composite BTC index, even if their charts look similar.

---

Fix time before interpreting price

There are two related but distinct time choices:

1. Candle time basis: the timezone and session convention that determine how the feed constructs or presents bars, particularly the daily and 4-hour bars.
2. Analytical session overlays: the windows you use to observe recurring liquidity, volatility, or execution conditions on intraday charts.

A display timezone alone is not necessarily a candle-construction rule. If a provider builds daily FX candles around a particular rollover, changing the time shown on your chart will not turn those candles into a different provider’s daily candles. Your contract should therefore record both the feed’s native session convention and the chart timezone used for review.

For your mix of FX, metals, and crypto, a practical baseline is:

• Chart display: UTC, for a stable and easily audited timestamp record.
• Session overlays: named regional zones using IANA notation, such as Europe/London and America/New_York.
• Daily and 4H candles: accept the selected provider’s actual construction. Record it; do not silently assume that a “New York close” chart is equivalent to another vendor’s daily chart.
• Crypto: explicitly state the daily anchor, normally UTC if that is the feed’s convention. Crypto trades continuously, but its daily candles still need a defined reset point.

The key operational implication is simple: if your session is meant to represent local New York hours throughout the year, write America/New_York, not a permanent UTC-4 or UTC-5. A fixed offset is acceptable only if you deliberately want a fixed offset.

Do not confuse an analytical session box with a structural boundary. A London or New York overlay can help you tag when a sweep or displacement occurs. It does not, by itself, make a high external or a break meaningful.

---

The contract: what must be written down

Use a plain-text note saved with your screenshots, replay file, and journal. It should be short enough that you actually maintain it.

CONTRACT ID: [market]_[feed]_[version date]

Market and execution reference
- Instrument: [exact symbol as displayed]
- Instrument type: [spot / CFD / futures / perpetual]
- Chart data provider: [exact provider or exchange]
- Execution venue: [broker or exchange]
- Price basis: [feed OHLC; note bid, ask, mid, or last if available]

Chart construction
- Chart type: standard time-based candlesticks
- Active session setting: [all sessions / regular session / provider default]
- Chart timezone: [UTC or named IANA zone]
- Daily rollover and 4H alignment: [provider convention, verified on chart]
- Missing-data policy: retain provider bars; do not manually repair gaps

Timeframe roles
- D1: external context ledger
- 4H: independent structure and intermediate context
- 1H: independent setup context
- 15m: execution structure
- Rule: no swing label transfers between timeframes

Structure vocabulary
- Pivot: defined only by the fixed pivot rule.
- External swing: a confirmed pivot promoted to the external ledger
  after it produces a qualifying structural break.
- Internal swing: a confirmed pivot retained in the internal ledger
  because it has not met the promotion rule.
- Protected swing: the active external swing whose qualified failure
  invalidates the current external directional state.
- Break qualification: to be fixed before replay begins.

The two lines that tend to be omitted, but matter most, are exact data provider and daily rollover / 4H alignment. Record them even when they feel obvious. In six weeks, “gold 4H” will not be enough information to reproduce a decision.

For live execution, the ideal chart source is usually the broker or exchange where you trade. If you use TradingView for analysis but execute elsewhere, document that mismatch. You can still trade it, but must test the method under the same mismatch rather than assuming the prices are interchangeable.

---

External, internal, and protected are roles, not sizes

The words are often taught visually: large swings are called external and small swings internal. That shortcut is precisely what creates hindsight-driven relabeling. On a 15-minute chart, a very large-looking pullback may still be internal; a relatively compact reversal can become external if it meets the promotion rule.

The operational distinction is based on ledger membership.

Term	Operational meaning in this course	What it is not
Pivot	A local high or low satisfying a fixed, later-defined pivot rule.	Any candle with a visible wick.
External swing	A confirmed pivot entered into the external ledger because it led to a qualifying external structural break.	The visually largest swing on screen.
Internal swing	A confirmed pivot recorded inside the active external development that has not earned promotion to the external ledger.	An unimportant swing.
Protected swing	The currently active external low in a bullish state, or external high in a bearish state, whose qualified violation invalidates that state.	A prediction that price can never trade through the level.

This creates an important discipline:

A swing can be visible before it is structural, and structural before it is protected.

For example, in a bullish external state, price may make several 1H pullback lows. They are initially pivot candidates. After the pivot rule confirms them, they may be logged as internal lows. The protected low remains the latest confirmed external low that launched the bullish external break. It is not replaced merely because a newer low looks clean on the chart.

The inverse applies in a bearish state: the protected high is the active external high whose qualified break would invalidate bearish external structure.

The phrase “protected” is best treated as an invalidation role, not a mystical support or resistance claim. If the protected level breaks under your predeclared break rule, the existing directional thesis is invalidated. The market is not “wrong”; your structure state simply has to change.

---

A useful convention from SMC, with a necessary restriction

The practitioner explanation in Justin Bennett’s video gives a useful core idea: an external high or low should not be confirmed solely because it looks like a swing. It needs to lead to a structural consequence. That aligns with the external-ledger promotion rule in this course.

“Liquidity sweep” is often useful descriptive language, but it is not yet an operational rule. Unless you specify:

• which prior internal pivot is the target;
• whether a wick is enough;
• whether a close is required;
• how far price must trade beyond it;
• and what timeframe supplies the evidence,

two analysts can see different “sweeps” in the same chart. We will solve the close, wick, and displacement questions in the next module rather than smuggling subjective judgment into the contract.

Protected swings are likewise commonly taught as points expected to hold during continuation.

For this course, use the narrower definition:

• A bullish protected low is the confirmed external low associated with the currently valid bullish external state.
• A bearish protected high is the confirmed external high associated with the currently valid bearish external state.
• It remains active until a later confirmed external continuation replaces it, or a qualifying contrary break invalidates it.

That rule provides an unambiguous answer to “which low matters?” without requiring you to treat every small 15-minute reaction as a new defended level.

---

Timeframe separation: four charts, four ledgers

Your intended workflow uses D1, 4H, 1H, and 15m. Keep them independent.

• The D1 chart defines daily external context.
• The 4H chart has its own pivots, external swings, internals, and protected level.
• The 1H chart has another independent ledger.
• The 15m chart supplies execution structure, not a miniature copy of the 1H labels.

A 15m low can be external on the 15m ledger while being invisible or merely internal on the 1H ledger. Neither label overrides the other, because each statement is conditional on its timeframe and candle construction.

For now, record the role of each timeframe but do not force them into a single hierarchy. The later multi-timeframe lesson will formalize how a daily context can constrain a 15m setup without transferring swing labels from one timeframe to another.

---

Implementation standard for this week

Before your next replay session, create one contract for one exact instrument you genuinely trade. Do not start with a watchlist. A good first choice is the specific gold, major-FX, or crypto-perpetual symbol on your actual execution venue.

Then:

1. Save a clean chart layout containing only standard candles, your selected feed, the fixed timezone, and session overlays if used.
2. Duplicate the layout for D1, 4H, 1H, and 15m.
3. Put the contract ID in each screenshot filename and replay journal entry.
4. If you change feed, session setting, timeframe alignment, or structural definition, increment the contract version and begin a new structure record.

Do not relabel old structure after changing a contract variable. That would merge two different datasets into one apparent strategy result.

---

A chart contract fixes the evidence before you read the story. Its essential commitments are: exact market and feed, stable time convention, explicit sessions, separate timeframe ledgers, and role-based definitions of external, internal, and protected swings.

Next, we will make the first of those definitions usable in real time: distinguishing a pivot candidate from a provisional extreme and a confirmed external swing, while refusing to use right-side information before it exists.