The engine behind every plan.
Before a BUY PLAN or SELL PLAN appears, the engine reads market behavior, checks location, confirms the VSA event, measures quality, tests target room, defines invalidation, and separates useful information from structured trade planning.
The visible label is only the final output. The real product is the decision pipeline behind it.
Nine discrete layers, executed in order. No layer is skipped, no result is forced.
CONF and PLAN are different outputs from different stages, with different meanings.
The same core is tuned per market — Gold, Crypto, Indices, and Forex — through edition-specific filters.
From raw market data to structured output.
- LAYER 01
Live Market Reading
Reads volume, spread, close position, candle result, and price reaction candle by candle. At this stage, the engine is not looking for an entry. It is collecting market evidence.
- Volume
- Spread
- Close position
- Candle result
- Effort vs result
Raw market evidence, nothing interpreted yet.
- LAYER 02
Context & Location
The same candle can mean different things in different places. The engine checks whether the event is near meaningful support, resistance, HTF levels, local structure, liquidity zones, or mid-range noise.
- HTF support / resistance
- Local structure
- Liquidity sweeps
- Range boundaries
- Mid-range caution
Same event at the wrong location is a different story.
- LAYER 03
VSA Clue Detection
The engine detects VSA-style clues such as spring, upthrust, absorption, buying climax, selling climax, no supply, no demand, range retest, and effort-vs-result failure.
- Spring / Upthrust
- Absorption
- Buying / Selling climax
- No supply / No demand
- Effort-vs-result failure
A clue is market information, not automatically a trade.
- LAYER 04
Confirmation Engine
After a clue appears, the engine checks whether price confirms the read through rejection, follow-through, failed progress, absorption response, or continuation behavior.
- Rejection
- Follow-through
- Failed progress
- Absorption response
- Continuation behavior
No confirmation means no trust.
- LAYER 05
Quality & Score Gates
Confirmed events are tested through quality gates. The engine checks score, location quality, strength of the read, market structure, regime, repeated-zone risk, and whether the setup deserves attention.
- Grade / Score
- Location quality
- Regime context
- Repeat-zone protection
- Market-specific filters
Not every confirmation deserves a plan.
- LAYER 06
Structure & Direction Check
The engine evaluates whether the plan is with the current structure, against the current drive, near a meaningful boundary, or too early. This is where many confirmed clues may remain CONF only instead of becoming a PLAN.
- With or against structure
- Counter-drive caution
- Boundary proximity
- Early-read flagging
Not every confirmed event deserves a structured plan.
- LAYER 07
Target Room & Invalidation
A plan needs space to work. The engine checks whether there is enough room to TP1, TP2, or TP3 and whether the invalidation level is logical.
- TP1 / TP2 / TP3
- Invalidation Area
- 1:1 Level
- Target expectation
- Invalidation logic
Invalidation is where the read stops being valid — not a random distance.
- LAYER 08
Warning & Caution Layer
The engine can highlight caution states such as early reversal, counter-trend context, broken structure, opposing HTF level, weak follow-through, or poor room. This helps the trader understand whether the read is clean, early, or higher risk.
- Early reversal caution
- Counter-trend caution
- Broken structure warning
- Opposing HTF level
- Poor target room
Caution is information, not a verdict.
- LAYER 09
Final Output
Only after the engine completes the process does it print the final output: CONF, No PLAN, or PLAN. CONF means useful market information. No PLAN means the engine saw something but did not structure it. PLAN means the event passed enough checks to become a planning reference.
- CONF · market information
- No PLAN · evidence without structure
- PLAN · planning reference
- Entry · Invalidation Area · 1:1 Level
- TP1 · TP2 · TP3
The final label is not an instruction. It is a structured decision-support output.
The journey behind every label.
Something meaningful happened. The market confirmed a VSA event, but that does not automatically mean a trade should be taken.
The engine found evidence, but one or more quality conditions were not strong enough. This is intentional. Silence and blocked plans are part of the discipline.
The confirmed event passed the engine's planning checks and is shown with Entry Reference, Invalidation Area, 1:1 Level, TP zones, quality grade, reason, and context.
Information is not the same as planning.
This is one of the most important parts of the engine. A VSA read can be useful even when it does not become a trade plan. Professional traders often notice market clues long before they are ready to execute. The engine reflects that discipline by separating information from planning.
The market may show early absorption, rejection, or exhaustion before a full structure shift. These reads can be useful, but they may still be higher risk.
A valid VSA clue in the wrong place can still be ignored. Location matters.
If the market does not offer realistic target room, a confirmed event may remain information only.
Read first. Plan second. Execute only when it makes sense.
The engine is designed to support professional decision-making. It helps organise market evidence, but the trader still checks context, structure, location, target room, and invalidation before execution.
The final trading decision always belongs to you. The engine sharpens the read — it does not replace judgment or risk management.
- 01Read the VSA clue.
- 02Check support / resistance and HTF location.
- 03Confirm whether the market responded.
- 04Review TP room and invalidation.
- 05Decide whether the plan makes sense for your risk.
A strong read can still fail.
VSA is a powerful market-reading method, but trading is still probabilistic. A read can make sense, confirmation can appear, and the market can still invalidate the idea. That is why the engine does not only show entries — it also shows invalidation, stop references, target zones, and caution states.
In VSA, the stop is not just a random price distance. It is the point where the read becomes invalidated.
What the engine actually draws.
- BUY CONF / SELL CONFA confirmed VSA event. Useful market information, not automatically a trade.
- BUY PLAN / SELL PLANA structured planning reference after additional quality checks. It includes context, target expectation, and invalidation logic.
- Invalidation AreaWhere the market read becomes invalidated — aggressive or wider depending on context.
- 1:1 LevelA neutral risk-to-reward reference for the plan.
- TP1 / TP2 / TP3Target zones based on the setup type, expected move quality, and available room.
- Dashboard & warningsQuick context for regime, location, volume, warning state, active case, and plan quality.
PLAN labels are structured decision-support references, not instructions to buy or sell. Always apply your own judgment and risk management.
Ready to use the engine?
Choose the edition that matches the market you trade.