One line, stage-dependent meaning

The Probability line uses the field relevant to the current lifecycle stage

Pattern Horizon does not treat every percentage as the same prediction. During CANDIDATE, FORMING, or AWAITING_CONFIRMATION, the Probability line uses formation probability when that field is available. The question is associated with the developing formation—not with guaranteed profit.

During CONFIRMED or BROKEN, the displayed probability is selected according to the realized Direction. If Direction agrees with Classical bias, the classical-direction probability is relevant. If the realized direction is opposite to the classical bias, the opposite-direction probability is selected.

For later states outside those groups, the renderer can use Confidence when a confidence score is available. At TARGET_REACHED, delivery routing can separately use primary target probability when configured. The key principle is that lifecycle and direction determine which available field is relevant; the headline does not represent one universal model output across every state.

Early lifecycle

Formation probability concerns the developing setup

A candidate pattern can have recognizable pivots and geometry before it is complete. Formation probability, when available, belongs to that early-stage question. It can help the system or user understand a developing candidate without pretending that confirmation or a target outcome has already occurred.

The value should be read with Status. AWAITING_CONFIRMATION still means the configured confirmation condition has not been recorded. Even a high formation probability cannot advance the lifecycle by itself. Price can fail to complete the structure, cross invalidation, expire, or break in an unexpected direction.

Formation probability is also not a personal trade success rate. It does not incorporate an individual's entry, exit, size, costs, or ability to execute. Use it as one structured field inside the signal, after verifying symbol, timeframe, pattern, Quality, and the condition being awaited.

After confirmation or break

Directional probability follows the realized direction—not just the textbook bias

Once a setup is CONFIRMED or BROKEN, the signal has realized directional evidence. Pattern Horizon compares that Direction with Classical bias. If they agree, the classical-direction probability is the relevant value. If the breakout occurred in the other direction, the opposite-direction probability is selected.

This design matters because patterns do not always resolve classically. A bullish textbook pattern can break bearish, or a bearish pattern can break bullish. Displaying only the classical-direction probability after an opposite breakout would answer the wrong question. Alignment records whether the relationship is CLASSICAL or OPPOSITE, while the Probability line follows the realized path when data exists.

Directional probability still does not guarantee that Target will be reached. Confirmation records a boundary event; follow-through, target, invalidation, and later context remain uncertain.

Later lifecycle fields

Confidence is not a substitute for every missing probability

For states outside forming and confirmed/broken selection, the signal presentation can use Confidence when a confidence score is available. This provides a later-stage field without pretending that formation probability or directional probability still answers the same question.

Confidence should remain attached to its definition and state. It is not automatically a calibrated chance of profit, and it should not be used to reconstruct a missing formation or target probability. If no corresponding value is available, the interface continues to show Not available yet.

Users should also distinguish the headline Probability line from the percentage displayed beside Target. The target suffix represents primary target probability when available. A message can therefore have a Target percentage while the general Probability line is unavailable. Those values come from different fields and should not be forced to match.

Keep the metrics separate

Quality, Probability, Confidence, and Target probability are not interchangeable

Quality evaluates structural fit under the rules, geometry, guidelines, or zone criteria applicable to the detection. Formation probability concerns the developing setup. Directional probability follows the classical or opposite realized path after confirmation. Target probability concerns the primary tracked objective. Confidence can be used for applicable later states.

Because they answer different questions, the numbers must not be averaged, added, multiplied, or ranked as though they formed a single universal score. Quality 90/100 plus a Target probability of 70% is not 160 points of confidence. Multiplying them does not create a supported 63% success rate.

A clean structure can fail; a medium-quality structure can reach its target; a high formation probability can remain unconfirmed; and a confirmed setup can invalidate before target. The lifecycle records these distinctions rather than hiding them behind one headline number.

Responsible interpretation

A percentage should be evaluated for calibration, coverage, and sample size

A useful probability model should be evaluated on outcomes collected under a fixed definition. Calibration asks whether events assigned similar probabilities occur at comparable frequencies over a sufficiently large sample. Coverage asks how often the field is actually available and which states, symbols, timeframes, and pattern families it represents. Sample size determines how much uncertainty remains around the observed result.

A report should state its period, dataset, target and invalidation rules, expiry handling, treatment of open setups, and whether probabilities were frozen before the outcome. Selecting only completed or favorable alerts would bias the analysis.

Even a well-calibrated market estimate does not predict an individual trade's net result. Execution costs, entry timing, order behavior, and account decisions sit outside the percentage shown in the signal. Historical calibration also does not guarantee future performance when market conditions change.

Common mistakes

Do not select the most attractive number and ignore its label

Avoid treating Quality as probability, Target probability as expected return, or Confidence as a universal replacement for unavailable fields. Do not read Not available yet as 50%, and do not interpret a high percentage as confirmation when Status still says AWAITING_CONFIRMATION.

Do not compare percentages across unrelated lifecycle stages as if they measured the same outcome. A formation estimate and a target estimate answer different questions. Do not assume that a displayed number already includes your spread, slippage, leverage, or risk tolerance.

Finally, do not judge accuracy from a few TARGET_REACHED screenshots. Include FAILED, INVALIDATED, EXPIRED, AMBIGUOUS, and unresolved signals under a predefined analysis. The field is useful only when its meaning and evidence remain visible.

Important information

Probabilities and confidence scores do not guarantee results

Pattern Horizon provides market information and educational content only. Quality scores, probability fields, confidence scores, targets, invalidation levels, directions, and statuses are not personalized investment advice and do not guarantee profit or prevent loss. Estimates can be unavailable, uncertain, or affected by changing market conditions.

Independently verify current prices and conditions, understand the instrument, and decide whether any setup fits your own method and circumstances. Account for liquidity, volatility, spread, slippage, leverage, and possible loss, and seek qualified professional advice where appropriate.