The method

Seven stages, in a fixed order, every session.

The One42 framework is a written process for reading NQ: what to mark before the open, how to read where price is, which side to expect next, what has to happen before an order is placed, what is decided in advance, and how the day gets judged afterwards. This page describes that process and the vocabulary it uses.

What this page is not

  • It does not tell you when to buy or sell, and it is not advice. Nothing here is tailored to you, your account, or your circumstances.
  • It does not claim the framework produces profits. Trade142 publishes no performance figures and no student results.
  • It does not include the framework's numeric thresholds — the point counts, the minimum sizes, the exact windows. Those are what the Core Program teaches.

Trading futures involves substantial risk of loss. Read the Risk Disclosure before applying anything on this page.

The sequence

Preparation, context, bias, execution, risk, review, improvement.

The order matters more than any individual rule. Each stage answers one question, and no stage is allowed to run before the one above it has an answer.

01

Preparation

What is already on the chart before the session opens?

Preparation happens before the market opens, not during it. The point is that by the time price starts moving, every level that matters is already drawn and already named. Nothing gets measured in the middle of a session.

Everything is done on the RTH chart — the regular trading hours chart, which shows only New York session data. The 24-hour electronic chart is deliberately not used for analysis, because overnight data changes which gaps look already filled and which levels look already taken.

The instrument is NQ. One market, one chart layout, one prep routine, run the same way every day.

The vocabulary

RTH chart
Regular trading hours only. New York data, nothing else. The framework's single source of truth for what has and has not been touched.
The prep sequence
A fixed order: measure the previous week, measure the previous day, establish the higher-timeframe direction, line out session highs and lows, mark rejection blocks, mark gaps, then check the economic calendar.
The calendar check
Scheduled economic releases are a prep step, not a surprise. The framework treats a release window as a reason to wait rather than a reason to trade.
02

Context

Where is price sitting relative to what came before?

Context is measured with a Fibonacci retracement, used for one thing: finding the 50% of a range. The previous week is measured low to high, and the previous day is measured low to high. The 50% of each is its equilibrium.

Above equilibrium is premium. Below equilibrium is discount. That is the whole vocabulary — the framework is not reading the Fibonacci levels as targets, it is using the midpoint to answer a location question.

Because two ranges are measured, price can be in premium of both, discount of both, or premium of one and discount of the other. The framework names each of those states and treats them differently.

Imbalances are marked in the same pass. A gap is an unfilled area left behind when price moved away quickly. Buy gaps and sell gaps are marked on the higher timeframes, and where two gaps from different timeframes overlap, the framework treats the overlap as the area of interest rather than either gap alone.

The vocabulary

Equilibrium
The 50% of a measured range. Marked for the previous week and the previous day, and treated as guard rails for knowing where you are.
Premium / discount
Above equilibrium is premium; below is discount. The framework's stated preference is to look for buys from discount and sells from premium.
Double premium / double discount
Premium or discount of both the previous week and the previous day at once. The framework treats agreement between the two ranges as a stronger location read than either alone.
Mixed range
Premium of one range and discount of the other. The framework names this state explicitly so it can be recognised as conflicted rather than mistaken for a signal.
Buy gap / sell gap
An unfilled imbalance left by a fast move. Marked on the 15-minute and 5-minute charts, and refined by dropping a timeframe to find where gaps overlap.
Inversion
The direction price returns from determines the reaction. A sell gap approached from above can invert and behave as support instead. The framework requires additional confirmation before treating an inversion as tradeable.
03

Bias

Which side is the market likely to reach for next?

Bias in this framework comes from liquidity, and liquidity means resting orders sitting above old highs and below old lows. Highs are buy-side liquidity; lows are sell-side liquidity. Once one side has been taken, the framework's expectation is that attention turns to the other.

Where those levels are drawn is the part that makes the framework distinctive. Levels are taken from candle bodies, not wicks. The reasoning James teaches is that wicks are where price fluctuated and bodies are where the volume actually settled — so the highest body in a session is the level that matters, not the highest print.

Liquidity is scoped by session. The New York day is split into named intra-sessions, each of which produces its own high, its own low, and its own body-based extremes.

The framework's hardest constraint sits here: if no liquidity has been taken, there is no trade. A setup that looks correct in every other respect is not taken without it.

The vocabulary

Rejection block high / low
The highest body and the lowest body within a session — not the highest and lowest wick. Labelled by session, so a chart carries an AM rejection block high, a lunch rejection block low, and so on.
Body over wick
The framework marks both the body extreme and the absolute wick extreme, but treats the body as where the real liquidity sits. A common error it names explicitly is waiting for the wick to be run when the body has already been taken.
AM session
9:30 a.m. to 11:59 a.m. New York time. The framework's primary session.
Lunch session
12:00 p.m. to 1:29 p.m. New York time. Treated as its own liquidity pool with its own rules, not as a quiet stretch of the AM.
PM session
1:30 p.m. to 4:14 p.m. New York time. Carries an extra confirmation requirement the AM does not.
Liquidity grab
A candle that opens on one side of a marked level and closes its body through it. That is the event the framework waits for — not a wick that pokes through and comes back.
In inventory
Once a side's liquidity has been taken, it is described as being in inventory. Inventory is what licenses the framework to start looking for an entry in the opposite direction.
04

Execution

What specific thing has to happen before an order is placed?

Execution is where the framework gets narrow. Having the right context and the right bias is not permission to enter — a named pattern has to appear, in a named sequence, at a permitted time.

The pattern is the One-For-Two signature, and it is worth being precise about what that name means. One For Two describes a three-candle shape, not a risk-to-reward ratio. A bullish signature is a low, then a lower low, then a higher low whose body closes back through the bodies of the first two candles. A bearish signature is the mirror of that. A candle that makes neither a new high nor a new low is skipped, which is why the pattern is sometimes four bars on the chart, and the framework caps it there.

The signature alone is not the entry. The sequence the framework requires is that a signature forms, that signature's own extreme gets run, and then a new signature in the same direction appears. That second signature is the trigger. Entering on the first one is the specific error the framework spends the most time warning about.

Timeframes are used as a hierarchy rather than as alternatives. The 15-minute is the bell weather chart, where the levels come from. The 5-minute is where the liquidity grab is confirmed. The 1-minute is where the entry is found — and the reason for dropping down is risk, because the same idea entered from a higher timeframe requires a far wider stop.

Time is a filter in its own right. The framework defines windows within every hour in which it will not take an entry, regardless of how good the setup looks, along with additional constraints around the lunch period and around scheduled news.

The vocabulary

The One-For-Two signature
A three-candle pattern (four with an inside candle skipped) whose final body closes through the bodies of the ones before it. A candle model, not a ratio.
The hunt
A signature forms, then its own extreme is run through. The framework treats the run as the market clearing the obvious level before it moves — and only then looks for the entry.
Fractal hunt in inventory
The confirmation requirement: a lower-timeframe signature, matching the intended direction, that has already been hunted before the entry is considered. No fractal hunt, no trade.
The LQG model
LQG is short for liquidity grab. Mark the levels, wait for a body close through one, log the inventory, then drop timeframes to find the signature. It is the framework's core execution model.
The bell weather chart
The higher-timeframe chart the day's levels are read from. Everything below it is monitoring and entry, not analysis.
The blackout window
Recurring minutes within each hour in which the framework forbids entry. It is a clock rule, not a judgement call, and it overrides an otherwise valid setup.
05

Risk

What is decided before the order goes in, and never after?

Risk in this framework is defined in advance and expressed in points, not as a feeling about how good a setup looks. The stop distance and the target are both fixed before entry, they are the same on every trade the model produces, and the stop is never widened once price is moving against it.

In the current version of the framework the trade is submitted with its stop and its target attached and then left alone. There is no moving to break-even, no adding to a loser, and no watching a position tick by tick looking for a reason to intervene.

Frequency is capped rather than left to discretion. The framework treats the session's first valid setup as the one to take and puts a limit on how many trades a day may produce — the constraint exists specifically so that a loss cannot be answered with another trade.

There is a distinction the framework insists on when a trade loses: whether it was a genuine loss, where the rules were followed and the market did something else, or an execution error, where a rule was broken. Only one of those is information about the model.

Nothing here is a claim about outcomes. A rule that caps risk limits how much a mistake costs. It does not make trades work.

The vocabulary

Fixed stop, fixed target
Both defined in points before entry, identical across trades from the same model, and not adjusted afterwards.
Submit and leave it
The order goes in with its stop and target attached. Management during the trade is treated as a source of error rather than a skill.
Genuine loss vs execution error
A trade that followed every rule and lost is data about the market. A trade that broke a rule is data about the trader. The framework grades every loss as one or the other.
Frequency cap
A hard limit on trades per session, in place so that revenge trading is a rule violation rather than a judgement call.
06

Review

What actually happened, judged against what was written down?

Review is done on the chart, not from memory. The session is replayed bar by bar, the day's context is re-derived from scratch, and each decision is judged against the rules as they were written — not against how the trade turned out.

Every trade is graded on the genuine-loss-versus-execution-error distinction. So is every trade that was not taken, because a valid setup that was skipped is as much a rule failure as an invalid one that was entered.

When the model produces an unusual result, the first thing checked is the economic calendar. The framework treats a scheduled release as a common explanation for a day that did not behave, and it would rather find that than invent a new rule.

The framework is also reviewed against itself over time — which model the current market is paying attention to, and which is being ignored. That is tracked as an observation, not converted into a prediction.

The vocabulary

Bar replay
Rewinding the session and re-deriving the read from the beginning, so the review is done without knowing what happened next.
Grade, do not rationalise
Each trade is scored against the written rules. A winning trade that broke a rule is still scored as an error.
Model rotation
An observation that market conditions favour different models at different times. Tracked in the journal; never used as a reason to override a rule.
07

Improvement

How does a trader get better at this without paying for it live?

The learning method the framework prescribes is forward testing: watching the market live, calling what the rules say, and not entering. James credits watching rather than trading as how he learned to read the market in the first place.

Backtesting is done the same way as review — day by day, marking each session's levels forward as it closes and rolling them into the next day, so the practice matches what live prep actually feels like.

The framework is deliberately kept small. The stated design principle is that it should not require micro-mechanics or sub-second judgement, because a rule you cannot execute under pressure is not a rule you have.

One more constraint belongs here: the framework does not try to predict the market beyond what its own model describes. Where the rules are silent, the answer is to stand down rather than to improvise.

The vocabulary

Forward testing
Watching live and calling the moves without entering. The framework's stated primary learning method.
Rolling backtest
Marking levels session by session as they close and carrying them forward, rather than reading a finished chart with hindsight.
Keep it simple
An explicit design constraint. The framework rejects additions that require reacting to sub-second chart fluctuations.
Do not predict beyond the model
Outside the situations the model names, the framework has no opinion, and the correct action is not to trade.

One naming note

"One For Two" is a candle pattern.

It is the name of the three-candle entry signature described in stage four. It is not shorthand for risking one to make two, it is not a risk-to-reward ratio, and it is not a claim about what any trade returns. The framework's stop and target are separate rules with their own numbers, taught in the Core Program.

The framework has versions

It has been revised, and lessons say which version they are.

James has changed parts of this model over time — which timeframe supplies the levels, which models he is actively trading, how entries are triggered. Material taught inside the Core Program is labelled with the version it belongs to, so nobody ends up running two different models as though they were one.

Where the tools fit

The indicators plot the stages, they do not replace them.

Each tool in the One42 suite draws or marks one part of this process on the chart. None of them decides whether a trade should be taken.

Premium/Discount Equilibrium Levels

Context — draws previous-day and previous-week equilibrium.

PD Array Gap Inversion Map

Context — marks buy and sell gaps and flags inversion behaviour.

Rejection Block Session Mapper

Bias — plots body-based session highs and lows for AM, lunch, and PM.

One-For-Two Signal Engine

Execution — marks and alerts occurrences of the entry signature.

LQG + Execution Filter Panel

Execution — surfaces the liquidity-grab model with its confirmation and time filters.

An indicator marking a pattern is a statement that the pattern is present, not a statement that a trade should be taken. See what is in each bundle.

Next

Read the framework, then decide which path you actually need.

Free content shows the process applied to real sessions. The Core Program teaches every rule and threshold in order. Mentorship is where your own execution gets reviewed against them.