FRACTAL AI AGENT Docs ← Terminal

Projection PRO

Forward price scenarios you can toggle through.

Projection draws three conditional price paths from the current chart—a base case, an opposing case and an extended case—so you can plan your response before price moves.

What this tool is for

Use it for scenario planning, not for finding a single “correct” future. It helps turn analysis into an if-then plan: if the base structure holds, follow one path; if the invalidation breaks, shift attention to the alternative.

How the paths are made

The tool reads the loaded OHLCV history and its calculated chart context—market structure, trend, ATR range, key support/resistance, detected patterns and Hurst behavior. From that context it builds three conditional paths: a base case, an opposing case and an extended case. Each path uses real price levels from the chart and includes a target, time in bars and an invalidation level.

This is not a single-line price forecast, a Monte Carlo simulation or a statistically audited probability model. The displayed percentages are the model's relative scenario weights for the current chart, so use them to compare branches and plan risk—not as a promise that a path will occur that often.

How to read the result

OutputWhat it means
Signal & confidenceThe overall directional lean and the clarity of the current evidence.
Fractal basisThe structural reason used to build the paths.
Scenario probabilityThe model's relative weighting of each path on the current chart. It is not a verified historical win rate or guarantee.
Projected pathA sequence of real price values drawn into the future area of the chart.
Bars & targetThe approximate horizon and destination for that scenario.
InvalidationThe price that would weaken or cancel the assumptions behind that path.
Entry zone & stopA possible execution framework shared with the current analysis.

Practical workflow

  1. Read the fractal basis and chart context before looking at the most attractive target.
  2. Toggle scenarios on and off to compare their paths without visual clutter.
  3. Write one condition that confirms and one condition that invalidates each scenario.
  4. Use the entry zone only if price behavior supports the associated path.
  5. Re-run after a breakout, breakdown or regime change because the original assumptions may no longer apply.
Think in branches: “If price holds above this zone, I manage toward the base target. If it loses the invalidation, I stop using that path and reassess.”
Projection is not prediction: the paths are planning aids generated from the loaded history. Exact turns, prices, timing and probabilities can be wrong.