Fibonacci Confluence Grids (Levels + Time Zones) [Metrify]This script is built around a simple but often-misused idea: Fibonacci levels are only useful when the reference swing is meaningful. In practice, most traders do not fail because they “used the wrong ratio,” but because they anchored the Fib to a weak or inconsistent swing. A 0.618 level drawn from noise is still noise.
The core design of this indicator is therefore not “draw more levels” but to formalize three simple steps that we usually do inconsistently by eye:
identify an A→B swing,
filter that swing for significance, and
project both price levels and timing windows from that swing.
Once a valid swing is accepted, the script projects a configurable set of price Fibonacci levels (retracements and/or extensions) and a separate configurable sequence of time gates (bar offsets projected forward from point B). The price levels define a vertical map of potential reaction zones. The time gates define a horizontal map of potential timing windows. Used together, they create a 2D framework: not only where price may become sensitive, but also when the probability of a market event tends to increase.
Time gates: temporal structure and why “events cluster” around them
The time gate projects vertical markers forward from point B using a bar sequence (commonly Fibonacci-like). The key idea is not random, but practical timing structure.
Markets often exhibit rhythm: impulsive legs, pullbacks, consolidations, and expansions frequently have characteristic durations.
Time gates should be interpreted as attention windows: periods where you should expect the probability of a notable market event to be higher than usual. “Event” here is intentionally broad, because direction is not guaranteed:
acceleration / continuation burst
pullback completion and resumption attempt
volatility expansion after compression
reversal attempt (successful or failed)
fakeout / stop run / liquidity sweep
structural break and regime shift
This is why it’s accurate to say that significant events often occur around time gates. Not because the gate forces a reversal, but because it’s a timing checkpoint where participation and auction dynamics frequently change. Your edge comes from combining the gate with context: price location near a major Fib level, session behavior, and confirmation from price action/structure.
How to use it as a manual framework
A strong discretionary workflow is to treat this as a 2D confluence map: price zone × time window.
Start by asking: “Is the active A→B swing meaningful?” If it looks like chop, tighten filters (increase Min Size / Min Bars, or increase ZigZag reversal / pivot length). Once the swing quality is good, treat the map as a set of planned observation points.
When price approaches a major retracement (0.5/0.618/0.786) or extension (1.272/1.618), check whether a time gate is also nearby. If yes, you should expect higher information density so you watch for confirmation rather than forcing prediction.
Confirmation can be whatever your style uses: structure break, reclaim, rejection candle quality, volatility expansion, etc.
If price is mid-range (far from major fibs) and far from gates, that’s often low-quality territory for forcing trades —> your standards should be higher, not lower.
Pine Script®指標
