Start with a published band and ask what historically happened after price first touched a specific depth.
Trading Terminal / How to use / Risk Management
Turn a first touch into a probability question.
A screen-by-screen guide to selecting a market, reading the Probability Map, separating model deadlines from chart windows, judging confidence, opening the expanded terrain and using Risk Control without confusing scenario evidence for a trade instruction.
The probability only makes sense after all four parts of the question are fixed.
Use the result as context. Return to the owning trade card for entry, stop, lifecycle and execution state.
Orient yourself on the loaded workspace.
The selected product, universe rail, surface timestamp, model horizon, price window, selected outcome and chart each answer a different question. Read them in that order.
The real product surface
This account-safe production capture shows Risk Management selected with AAPL loaded. The universe stays on the left; the Probability Map uses the full analysis area on the right.
Know exactly what question the product answers.
Risk Management estimates a conditional outcome after a published band is touched. It does not forecast the next candle, promise a destination or issue a trade instruction.
Start with the current surface, side and published lower or upper edge.
The event is defined by target, exact first-touch price and band-width depth.
Read the estimated recovery or retrace probability, confidence interval and sample size.
Conditional evidence
“After this first touch, how often did the selected outcome occur by this exact deadline?”
Expected path
The shaded terrain is not a projected route for the next candles and the probability is not an expected price.
Guaranteed level
A high probability does not make the target certain or remove loss and gap risk.
Trade authority
The surface never creates, updates or closes a Terminal trade.
Select one covered market deliberately.
The universe rail controls which surface is loaded. Search and filters narrow the list; the checked selector identifies the active market.
Read the Probability Map from the header down.
The map header establishes market, side and freshness. Controls define the question. The selected-outcome strip answers it. The chart shows the observed context and published deadline terrain.
Put the first-touch condition before the percentage.
A probability without its target, depth and deadline is incomplete. The map conditions on price first reaching one published depth around the selected band.
Target
Choose lower/reclaim or upper/retrace on the current long-side surface.
First-touch price
The published level at which the conditional sample begins.
Depth
The touch is expressed in band widths so shallower and deeper points remain comparable.
Deadline
The result belongs to one exact cell. Do not interpolate a probability between published horizons.
Read one selected outcome completely.
Do not stop at the large percentage. The target, horizon, first-touch level, normalized depth, interval, sample and stability state complete the evidence.
| Readout | Question it answers | Common mistake |
|---|---|---|
| Probability | How often did the selected outcome occur after this first touch? | Treating it as certainty or expected return. |
| Outcome | Is the sample counting reclaim or retrace? | Reading the same percentage as both outcomes. |
| Deadline | By which exact published horizon? | Assuming a 720m cell implies the 60m result. |
| First-touch level | Where does the condition begin? | Treating the level as an order or current stop. |
| Band-width depth | How far into or beyond the band is the touch? | Comparing raw dollars across unlike markets. |
| Confidence interval | How wide is the uncertainty around the estimate? | Ignoring a wide interval because the headline is high. |
| Sample size | How much historical support contributes? | Equating a small sample with a well-supported cell. |
Never confuse probability deadlines with price windows.
The two control groups sit together but do different jobs. One changes the model question; the other changes only the chart context.
Each button selects one discrete published probability cell. Switching from 60m to 720m can change probability, interval, sample, stability and deadline terrain.
These buttons change how much observed price history surrounds NOW. They do not recalculate the selected 720m probability or create a new model horizon.
Read lower support and upper resistance on the current long-side surface.
The public release currently presents a long-side surface. Lower touches ask about reclaiming the range; upper touches ask about retracing to the upper edge.
Condition on a published lower depth and count whether price reclaims the range by the selected deadline.
Model reference, lower edge, mid band and upper edge define the current surface geometry.
Condition on a published upper depth and count whether price retraces to the upper edge by the selected deadline.
Use Probability Map and Model Curves for different jobs.
The map is best for one selected point in price context. Model Curves are best for comparing how the complete probability profile changes across depth and horizon.
Judge support, not just the headline.
Confidence comes from the interval, sample size and structural support together. The interface fades or hatches weak areas so uncertainty remains visible.
The estimate is better supported within the current surface. It is still probabilistic and can fail.
Keep the uncertainty range beside the headline and avoid false precision.
The map can mark a structural cliff when probability falls below support thresholds. Do not treat the cell as a clean setup.
What “map valid / stable” actually means
Inputs are usable
The selected surface cell has the required published fields and can be rendered.
Statistical support
Sample and interval support clear the current stability criteria.
No market guarantee
Validity does not certify the trade, eliminate tail risk or promise the selected outcome.
No streaming claim
The surface can be a dated model snapshot while chart context updates on a separate cadence.
Use Risk Control as scenario evidence—not an order ticket.
Risk Control translates the selected surface into current, band, reduce, exit and target levels. Those levels help frame conditional risk; they do not automatically replace a trade card's active stop.
Separate surface freshness from price freshness.
The probability surface, delayed candle feed and optional trade context have separate sources and clocks. The page exposes those boundaries so a partial source failure stays honest.
As-of date
The dated probability snapshot used for the selected market. It is current-surface evidence and is never backfilled across the historical candle path.
Build time
When the current surface was calculated. This is not the same as the most recent candle.
Delayed context
Candles and delayed last can update independently and are reference data rather than a broker feed.
Optional overlay
Entry context can help choose the initial window but never becomes trusted trade state inside the map.
Honest degraded states
Keep the exact probabilities and source status visible; do not hide valid model evidence because candles failed.
Show the fallback source and dated as-of/computed fields. Never describe it as a fresh live surface.
Show unavailable and stop. Do not synthesize a range, probability or substitute ticker.
Use a neutral chart window such as 1D. Do not invent entry or position state.
Use the same 60-second workflow every time.
The order matters because each step prevents a common category error: wrong ticker, wrong target, wrong horizon, unsupported headline or mistaken trade authority.
Section 06 must be selected and the large ticker header must match the market you intend to study.
Confirm the current public long-side surface, surface as-of date and computed time.
Lower/reclaim or upper/retrace defines the counted outcome; depth defines the first-touch condition.
Select 60m, 720m, 5d or 20d. Never infer an unshown in-between probability.
Probability, target, first-touch level, depth, confidence interval, sample size and stability belong together.
Entry for a valid attached entry; otherwise 1D, 5D, 1M or 3M for context. This does not change the probability.
Use the lens for exact terrain and Model Curves for profile comparison, then return to the selected point.
If a live trade is involved, verify current state and active SL on its owning card before taking any action.
Use the mobile map as a focused point reader.
Mobile stacks the workspace into one column. It keeps ticker, horizon, price window, selected outcome, target and depth controls, while hiding the desktop Model Curves switch.
Mobile-specific rule
Use the right authority and keep every boundary visible.
The product is strongest when the conditional question is precise and the result stays in its lane. Use these checks before relying on a surface.
Confirm the market
Ticker header and selected rail row must agree after every switch.
Name target and touch
Lower/reclaim or upper/retrace, exact level and band-width depth come before probability.
Use one published cell
60m, 720m, 5d and 20d remain discrete; price windows are separate.
Read CI and N
Stability is statistical support, never a guarantee or safety label.
Common questions
Is the Probability Map predicting the next price path?
No. It estimates a conditional recovery or retrace outcome after a first touch. Price is the vertical axis and the future horizontal axis contains exact deadlines, not projected candles.
Does a 65% 720m result imply the 60m probability?
No. Each horizon is a separate published cell. Select 60m to read the 60m result.
Does choosing 5D in the price window change the 5d probability?
No. 5D in Price Window changes candle history. 5d in Model Horizon changes the probability deadline.
Is “map stable” the same as “safe trade”?
No. Stable describes statistical support for the selected cell. It does not certify a trade or remove market risk.
Is Risk Control's exit level my active Terminal stop?
Not automatically. Risk Control supplies scenario evidence. The owning trade card remains the authority for the published active SL.
Why do the surface date and candle time differ?
They come from separate source chains. The probability surface is a dated model snapshot; delayed price context can update independently.
What should I do if the chart fails but probabilities remain visible?
Use the probability values only with their exact source, date, target, depth and deadline. Treat the missing chart as unavailable reference context rather than discarding valid surface data.
What if my ticker has no surface?
Respect the unavailable state. Do not invent a substitute range or transfer values from another ticker.
Can Risk Management open, update or close a trade?
No. It supports risk analysis only. Trade cards, Alert Log and Performance retain lifecycle authority.
Ready
Open Risk Management with the condition fully defined.
Confirm the market, surface date, target, first-touch depth and exact horizon. Then read probability, interval and sample together—and return to the owning trade card for live state.