PRZ Execution

PRZ Execution starts where pattern recognition stops — the first library tool dedicated to PRZ execution, managing price from arrival in a potential reversal zone to a graded outcome. Auto mode projects a completion window past the latest X-A-B-C swings from XA ratios, plus a limiting level; Manual mode takes any measured zone. From first touch a state machine runs — test, terminal price bar, entry, resolution — tracked in a status table.

How to Trade the PRZ Execution?

• Terminal price bar: tests the whole zone and is graded on its close — back toward structure is constructive, wide beyond it the classic warning; both alerted.
• Entry confirmation: the default waits for terminal-bar rejection; Close back inside structure is earlier, First zone touch mimics a limit at D.
• Type I vs Type II: a prompt reaction that stays clear of the zone is Type I; a retest that holds near the original extreme and rejects is Type II — deep retests demand more evidence.

PRZ Execution Settings

• Zone source (default Auto (harmonic completion window)).
• Swing pivot length (default 8): pivot confirmation bars.
• Completion ratio - near edge (default 0.786) and Completion ratio - far edge (default 0.886).
• Invalidation ratio (limiting level) (default 1.0): the void level (X for retracements).
• Manual - direction, Manual - zone edge A / B, Manual - invalidation level (0 = auto).
• Entry confirmation (default Terminal bar rejection).
• ATR length (default 14), Wide bar threshold (x ATR) (default 1.5), Reaction distance (x zone height) (default 2.0) and Type I: bars clear of the zone (default 10).
• Retest tolerance (x zone height) (default 0.5), Closes beyond limit to invalidate (default 2), Episode timeout (bars) (default 100) and Max acceptable stop distance (%) (default 2.0): wider zones grade "too wide, pass".
• Display toggles for labels, table, zone transparency.

Frequently Asked Questions

How does this relate to pattern detectors like the Crab?

A detector such as the Crab finds the five points and draws the completion zone; it does not say what to do when price arrives. This build owns that second half; manual mode manages a zone from any pattern.

Why two closes to invalidate instead of one?

Zones are routinely wicked through, so the limiting level voids the pattern only on decisive acceptance — consecutive closes beyond it. A violated zone is itself trend-strength information.

What happens if the test never resolves?

After the timeout an unresolved episode closes with an Expired tag. The build re-arms on the next qualifying sequence or, in manual mode, once price clears the zone again.