cephxs / Risk Calculator [Pro +]Risk Calculator
Type your stop in ticks and the dollars you accept to lose. The table tells you how many contracts fit, and what those contracts actually risk.
WHAT IT DOES
Position sizing is the one calculation that decides whether a losing streak is survivable, and it is the one most people do in their head, wrong, on the way into a trade.
This is a manual sizer. Two inputs, one small table, nothing else on your chart. No signals, no boxes, no arrows, no alerts. It reads the symbol you are on, converts your stop from ticks into dollars, and reports how many contracts fit inside the risk you set.
It reports both the standard contract and its micro sibling, side by side, every time. There is no micro toggle to remember, because the choice between one mini and twelve micros is a trading decision, not a setting. This tool is calibrated specifically to Futures contracts, Updates will follow soon for support for Forex CFD Lots and instructions on how to understand them and speed up your trading for cross platform trading (externl execution and PulseWire charting for example.)
HOW IT WORKS
Three ideas, and the third is the one that gets sizers wrong.
1. Ticks, not points. You think in ticks, because that is what your stop is measured in on the DOM. Contract specifications are quoted per point . The script converts between them using the symbol's own tick size, so a 50-tick stop on CME_MINI:RTY1! (0.1 tick) and a 50-tick stop on CME_MINI:ES1! (0.25 tick) are correctly priced as different distances instead of being treated as the same number.
2. A contract pair, not a contract. The script carries a lookup of index, metal, energy and FX futures. Each entry stores the dollar value of a one-point move for the standard contract and for its micro. The same pair resolves whichever side of it you are charting: load CME_MINI:NQ1! or load CME_MINI:MNQ1! and you get the same two columns, in the same order. Micro tickers are matched before their standard root, so CME_MINI:MNQ1! is never mistaken for the CME_MINI:NQ1! entry.
3. Floor division, and no rounding up. Contract counts come from your risk budget divided by the dollar cost of one contract at your stop, rounded down . A partial contract is not a contract. This means the reported figures are never the budget read back at you — they are what the position genuinely risks, which is at or under the budget by the size of the remainder.
HOW TO READ THE TABLE
Four stacked rows. The example below is a 25-tick stop with a $400 budget on CME_MINI:ES1! (Same as the publication Screenshot):
ES1!
25 ticks
$313 / $375
1 mini / 12 micros
Row 1 — Asset. The symbol the numbers were computed for. Confirms the script resolved what you think it resolved.
Row 2 — Stop. Your stop, as typed.
Row 3 — Risk. What each position actually loses if the stop is hit.
Row 4 — Size. What to place.
Rows 3 and 4 are a pair and read column for column. Standard contract on the left, micro on the right. $313 is what that 1 mini risks. $375 is what those 12 micros risk. Both sit under the $400 budget. Neither is the budget itself.
The colors are the warnings.
Grey — normal. Both sides are tradeable.
Amber — one standard contract already exceeds your budget. Its count reads 0. Only the micro column is tradeable.
Red — even one micro exceeds your budget. Row 4 reads "Risk too big", and row 3 switches to showing what one of each contract would cost, so you can see how far over you are.
Every cell carries a tooltip with the full arithmetic: ticks, dollars per tick, dollars per contract, and the budget the counts were divided by. Hover it when a number surprises you.
HOW TO USE
Load it on the futures contract you trade.
Set Preferred Risk once. This is your per-trade loss limit in dollars, and it should not change trade to trade.
Before each entry, set Stop Size to where your stop actually goes — below the swing, past the level, wherever your method puts it. Do not pick the stop that makes the size convenient.
Read row 4 and place that size.
If the block turns red, the trade is not untradeable — the stop is too wide for your account at this risk. Wait for a tighter structure rather than moving the stop in.
The order matters. Risk is fixed, stop is dictated by the chart, and size is the output of those two. Sizing first and then hunting for a stop that fits is the habit this table exists to break.
INPUTS
Stop Size (ticks): 25. Distance to your stop, in ticks. Drives everything. Fully customizable.
Preferred Risk ( AMEX:USD ): 400. Maximum dollars you accept to lose. Both contract counts stay at or below it. Add a small leeway $50 if you're willing to get even closer to your preferred risk.
Table Position: Bottom Left. Any of the nine pane anchors.
Layout: Values Only, or Labeled (adds a dimmed caption column).
Text Align: Left, Center, Right. Applies to the value column.
Edge Padding (rows): 2. Blank rows between the block and the pane edge it hugs. Inert on the three Middle positions, which have no edge to lift off.
Text / Warn / Error colors: the three states above, in that order.
Table Text Size: Standard. Compact through Extra Large, or Auto.
The table draws as plain text with no background and no border, so it sits on the chart without covering price.
SYMBOLS COVERED
Indices: CME_MINI:NQ1! · CME_MINI:MNQ1! · CME_MINI:ES1! · CME_MINI:MES1! · CBOT_MINI:YM1! · CBOT_MINI:MYM1! · CME_MINI:RTY1! · CME_MINI:M2K1!
Metals: COMEX:GC1! · COMEX_MINI:MGC1! · COMEX:SI1! · COMEX_MINI:SIL1! · COMEX:HG1! · COMEX_MINI:MHG1!
Energy: NYMEX:CL1! · NYMEX:MCL1! · NYMEX:RB1! · NYMEX:HO1!
FX: CME:6E1! · CME_MINI:M6E1! · CME:6B1! · CME_MINI:M6B1! · CME:6C1! ·
NYMEX:RB1! and NYMEX:HO1! have no micro, so they report a single column. Every other symbol reports the pair.
LIMITS — read these
It does not know your account. There is no balance, no margin check, no daily loss limit. If your broker's day-trade margin will not carry 12 micros, the table will still say 12. That number is what your risk allows, not what your buying power allows.
It does not know your position. It is a pre-trade calculator, not a position tracker. It never reads open orders or fills.
Commissions and fees are excluded. Twelve micros cost meaningfully more in round-turn fees than one mini for the same risk. That gap is real and this table does not show it.
Off-list symbols degrade, they do not fail. On anything outside the list above, the script falls back to the symbol's own point value, finds no sibling, and collapses to a single column labeled in plain "contracts". Stocks, crypto and forex spot will produce a number this way. Confirm it against your broker before you trade it.
Futures-first by design. The tick-to-dollar chain assumes a contract with a fixed point value. It is not a share sizer.
No performance claim is made or implied. Correct sizing controls the size of a loss. It does not make a losing setup profitable.
FAQ
why does it show both minis and micros instead of picking one?
Because the right answer depends on what you are doing, not on the arithmetic. Twelve micros let you scale out in twelve pieces and cost more in fees. One mini is cheaper and all-or-nothing. The table gives you both and stays out of the decision.
why is the risk figure lower than my preferred risk?
Rounding down. If one contract costs $400 and your budget is $500, one contract fits and $100 goes unused, because 1.25 contracts do not exist. The figure shown is the real risk of the real position.
it says "Risk too big" — is something broken?
No. One micro at your current stop costs more than your entire budget. Either the stop is wider than your account can carry at that risk, or the risk input is set low. Row 3 shows what one of each contract would cost, so you can see the gap.
does it repaint?
There is nothing to repaint. The table is computed on the last bar from your two inputs and the symbol's specification. It uses no history, no higher timeframe requests and no future data.
my broker's contract value differs from the table.
Trust your broker. Contract specifications change and exchanges list variants. The tooltip shows the exact dollars-per-tick used, so you can compare in one look.
DISCLAIMER
This script is a calculator. It gives no trade signals and makes no forecast. Contract specifications are hardcoded and can become out of date, and off-list symbols use a fallback value — always confirm the numbers against your broker before you place an order. Trading futures involves substantial risk of loss and is not suitable for every investor. Nothing here is financial advice.
Open source under the Mozilla Public License 2.0. Read the code, fork it, change the contract table to suit your instruments.
Indicator
Indicator
Risk Guard - Position Size & Risk CeilingWhat it does
Risk Guard sizes your position from the risk you are willing to take, and tells you immediately when that risk goes above the limit you set for yourself.
Most position size calculators stop at the arithmetic. This one adds the part that actually protects an account: a ceiling.
Why a ceiling
Many traders do not use a fixed risk per trade. They size up on strong setups and down on weak ones. That flexibility is fine, until one trade quietly goes far beyond what the account can absorb.
Risk Guard separates the two:
- Risk for THIS trade is what you are taking right now, and it can change every time.
- Your risk ceiling is your rule, and it does not change.
When the first goes above the second, the table switches to the alert colour and says so plainly.
How to use it
1. Add the indicator. It displays straight away, using the current price and one ATR as demonstration values, so you never face an empty table.
2. Open the settings and enter your own Entry and Stop in the Trade group. Add a Target if you want R:R.
3. Set your account size, the risk for this trade, and your ceiling.
4. Pick the sizing mode and the pip size that match your instrument.
Sizing modes
Lots: gold, forex, CFD. Set the contract size (XAUUSD standard is 100 oz per lot, forex standard is 100000).
Units: crypto and spot.
Whichever you pick, the position size is shown with its unit spelled out and the other unit in brackets, so it cannot be misread.
What it shows
Direction, account size, trade risk against your ceiling, amount at risk, stop distance in price and in pips, position size, R:R and gain at target.
Customisation
Every colour is configurable: header within limit, header when the ceiling is passed, table background, text, position size value, and the entry, stop and target lines. Text size, border width and table position can also be changed.
Notes
Pip size is a setting, not a guess: gold 0.1, forex majors 0.0001, JPY pairs 0.01, and 0 to hide pips on crypto.
The calculation is exact when the quote currency matches your account currency. On crosses where it does not, treat the result as an approximation.
This is a planning tool. It does not place orders and does not read your broker account.
Indicator
Liquidity Thermodynamics Engine V9 LiteLiquidity Thermodynamics Engine V9 Lite is a macro-liquidity oscillator designed to highlight liquidity impulse, acceleration, compression, divergence, and follow-through conditions. It is a lite core version of a more heavy research model that explores liquid thermodynamic phase models as the physics corresponds to capital flows.
The indicator combines major liquidity inputs into a normalized composite, then tracks when liquidity impulse strengthens, compresses, diverges from price, or aligns with acceleration. The Lite version focuses on a clean chart experience while preserving an optional Flow Map for users who want to inspect the underlying liquidity drivers.
Primary signals include:
- Composite and signal line
- Positive and negative impulse histogram
- Bright positive impulse bars
- Acceleration markers
- Compression diamonds
- Bullish and bearish divergence markers
- Bright green follow-through triangle
- Optional energy exhaustion flag
- Optional Flow Map
This tool is intended for macro context and research. It is not financial advice and should not be used as a standalone trading system.
User Guide
Liquidity Thermodynamics Engine V9 Lite, or LTE Lite, is a macro-liquidity momentum oscillator designed to help users visualize when liquidity conditions are compressing, accelerating, diverging from price, or beginning to follow through.
The indicator is not designed to predict every short-term move. It is best used as a higher-timeframe liquidity context tool, especially on slower charts such as the 6D, weekly, or multi-day Bitcoin chart. Its strongest signals tend to come when liquidity impulse and acceleration align near important macro turning zones.
This guide explains what each signal means, how to read the chart, and how to use the tool responsibly.
1. What LTE Lite Measures
LTE Lite combines several macro liquidity series into a normalized oscillator:
- Federal Reserve total assets
- Treasury General Account
- Overnight reverse repo
- Reserve balances
- Optional inverse DXY overlay
The core model converts liquidity conditions into a composite line, then measures the speed and force of changes in that composite. The result is a compact view of liquidity pressure, impulse, acceleration, compression, divergence, and exhaustion.
In simple terms:
- The white line shows the liquidity composite.
- The yellow line smooths that composite into a signal line.
- The histogram shows liquidity impulse.
- Markers highlight important changes in pressure, momentum, divergence, and exhaustion.
2. The Core Lines
White Line — Composite Line
The white line is the main liquidity composite. It represents the current normalized liquidity condition.
When the white line rises, liquidity conditions are generally improving. When it falls, liquidity conditions are generally deteriorating.
The white line is more reactive than the yellow signal line.
Yellow Line — Signal Line
The yellow line is a smoothed version of the composite.
It helps users distinguish noise from directional liquidity movement. When the white line rises above the yellow line, liquidity momentum is improving. When the white line falls below the yellow line, liquidity momentum is weakening.
The signal line is not a trade trigger by itself. It is context.
3. Impulse Histogram
The histogram measures the rate of change in the liquidity composite.
Green Histogram Bars
Green bars show positive liquidity impulse.
This means liquidity pressure is improving relative to the prior bars.
Red Histogram Bars
Red bars show negative liquidity impulse.
This means liquidity pressure is deteriorating.
Bright Green Histogram Bars
Bright green bars mark stronger positive impulse.
By default, LTE Lite highlights positive impulse bars when they reach or exceed the Key Positive Impulse Level. In the current stock configuration, this level is set to `0.10`.
These bars are important because they often mark a stronger liquidity push rather than a minor improvement.
Important: a bright green histogram bar is not automatically a buy signal. Its value increases when it aligns with acceleration, compression release, improving structure, or price confirmation.
4. Acceleration Markers
Acceleration markers show when the impulse itself is accelerating.
Yellow `+`
A yellow plus sign marks positive acceleration.
This means liquidity impulse is not just positive; it is improving quickly enough to clear the acceleration threshold.
Positive acceleration can appear before a larger histogram impulse bar, or the impulse bar can appear first. LTE Lite watches for either order.
Yellow `-`
A yellow minus sign marks negative acceleration.
This means liquidity impulse is weakening quickly.
Negative acceleration can warn that a prior liquidity push is losing force.
5. Bright Green Triangle Signal
The bright green triangle is one of the most important Lite signals.
It fires when:
- A bright positive impulse bar occurs, and
- A positive acceleration signal occurs, and
- The two events happen within the configured window.
The default window is `7` bars.
On a 6D chart, 7 bars is roughly 42 calendar days. This gives the signal room to capture cases where acceleration leads impulse and cases where impulse leads acceleration.
Why This Signal Matters
This signal is designed to identify liquidity follow-through.
The idea is:
- A large positive histogram bar shows meaningful liquidity impulse.
- A `+` acceleration marker shows liquidity momentum is expanding.
- When both appear close together, the market may be entering a more supportive liquidity window.
This does not guarantee immediate upside. It means liquidity conditions have improved enough to deserve attention.
How to Use It
Best practice:
1. Watch for the green triangle on higher timeframes.
2. Check whether price is basing, breaking structure, or reclaiming key levels.
3. Confirm that the composite is stabilizing or rising.
4. Avoid treating the triangle as a standalone entry signal.
The green triangle is a context signal, not a mechanical trading command.
6. Compression Signal
Compression is shown as a small gray diamond around the zero line.
Compression appears when:
- Liquidity impulse is small, and
- Composite movement is also muted, and
- This quiet condition persists for the configured number of bars.
Compression means liquidity energy is coiling.
It does not tell direction by itself. It simply says the system is quiet enough that a larger move may be building.
How to Use Compression
Compression is most useful when followed by:
- Positive acceleration
- Bright green impulse
- A green triangle signal
- Composite reclaiming or curling upward
Compression followed by negative acceleration can instead warn of downside continuation.
7. Divergence Signals
Divergence compares price structure against liquidity structure.
Bullish Divergence
A bullish divergence marker appears when price makes a lower pivot low while the liquidity composite makes a higher pivot low.
This can suggest that price is weakening less efficiently because liquidity conditions are improving underneath the surface.
Bearish Divergence
A bearish divergence marker appears when price makes a higher pivot high while the liquidity composite makes a lower pivot high.
This can suggest that price is rising while liquidity support is weakening.
Divergence Mode
The default mode is:
`Price vs Liquidity + Impulse`
This is stricter than simple price-versus-liquidity divergence because it also checks impulse direction. The goal is to reduce noisy divergence signals.
Divergence is best used as a warning or confirmation tool, not as a standalone entry or exit.
8. Energy Exhaustion Flag
The Energy Exhaustion Flag is an optional marker.
It is designed to identify moments when internal liquidity energy has dropped sharply or clustered into a weak state.
By default in the current V9 Lite stock settings, this marker is turned off.
When enabled, it can help identify late-stage exhaustion after strong liquidity movement. It should be used carefully because exhaustion can persist before price responds.
9. Flow Map
The Flow Map is an optional visual layer.
It breaks liquidity movement into individual components:
- Fed flow
- Treasury flow
- RRP flow
- Reserve flow
The Flow Map helps users see which component is contributing most to liquidity movement.
Flow Map Modes
`Stacked Bars` shows all selected flow components.
`Dominant Bars` shows only the strongest component on each bar.
`Stacked + Dominant Marker` shows the flow bars and adds a marker to the dominant component.
How to Use the Flow Map
Use the Flow Map when you want to inspect what is driving the oscillator.
For example:
- Reserve flow may dominate during banking-system liquidity shifts.
- TGA changes may dominate around Treasury cash rebuilding or drawdowns.
- RRP shifts may dominate when reverse repo usage changes materially.
- Fed balance sheet changes may dominate during major policy/liquidity events.
For clean chart reading, leave Flow Map off. Turn it on when doing deeper diagnostics.
10. Suggested Timeframes
LTE Lite is designed primarily for higher-timeframe liquidity analysis.
Recommended starting points:
- Bitcoin 6D
- Bitcoin weekly
- Major index weekly
- Multi-day charts for macro context
Lower timeframes may produce more noise because macro liquidity data updates slowly relative to intraday price action.
The 6D chart can be especially useful because it balances signal sensitivity with macro smoothness.
11. Practical Reading Workflow
Use this sequence:
Step 1 — Identify the Liquidity Regime
Look at the white and yellow lines.
Is the composite rising, falling, basing, or rolling over?
Step 2 — Check Impulse
Look at the histogram.
Are bars green or red? Are green bars brightening? Is negative impulse fading?
Step 3 — Watch Acceleration
Look for `+` or `-` markers.
A `+` means liquidity momentum is accelerating. A `-` means it is decelerating.
Step 4 — Look for Follow-Through
The green triangle is the key combined signal.
It means strong positive impulse and positive acceleration have occurred within the configured window.
Step 5 — Confirm With Price
Do not use the indicator alone.
Look for price confirmation such as:
- Break of market structure
- Reclaim of key moving averages
- Higher lows
- Range breakout
- Failed breakdown
- Support reclaim
Step 6 — Manage Risk
Liquidity support can improve before price moves. It can also improve while price continues consolidating.
Use invalidation levels, position sizing, and a clear plan.
12. Signal Priority
Not all signals carry equal weight.
Highest priority:
1. Bright green triangle after or near positive acceleration
2. Bright green impulse bars appearing after compression
3. Bullish divergence near a major low
4. Composite rising above the signal line
Medium priority:
1. Positive acceleration without bright impulse
2. Compression alone
3. Flow Map showing improving dominant flow
Lower priority:
1. Small green histogram bars
2. Isolated divergence without impulse confirmation
3. A single marker against strong price downtrend
13. Common Mistakes
Mistake 1 — Treating Every Green Bar as Bullish Enough
Small green bars only show mild improvement. The brighter bars matter more.
Mistake 2 — Ignoring Timeframe
Signals on a 6D or weekly chart are not short-term scalping signals. They describe larger liquidity conditions.
Mistake 3 — Ignoring Price Confirmation
Liquidity can lead price, but price still needs to confirm.
Mistake 4 — Assuming the Triangle Means Immediate Upside
The triangle identifies a supportive liquidity window. It does not guarantee immediate price expansion.
Mistake 5 — Overloading the Chart
Keep Flow Map off unless you are diagnosing components. The cleanest read usually comes from the composite, signal line, histogram, acceleration markers, compression, divergence, and green triangle.
14. Default Settings Philosophy
The stock settings are tuned for a clean macro read.
The defaults prioritize:
- Higher-timeframe stability
- Fewer false signals
- Visibility of major impulse events
- Clean chart presentation
- Optional component diagnostics through Flow Map
If users modify settings, they should do so slowly and test across multiple cycles.
Risk Disclaimer
This indicator is for educational and research purposes only.
It does not provide financial advice, investment advice, or trading recommendations. Markets involve risk, and no indicator can guarantee future performance. Users should combine this tool with independent analysis, risk management, and their own decision-making process.
Past signal behavior does not guarantee future results. Indicator
ATR Chandelier StopTrade Control Adaptive ATR Chandelier Stop
The Trade Control Adaptive ATR Chandelier Stop is a volatility based trailing stop designed for swing and position traders who want a more objective way to manage exits and protect gains.
Instead of applying the same fixed percentage stop to every stock, the indicator uses Average True Range, or ATR, to account for how much each symbol typically moves. More volatile stocks receive wider stop levels, while lower volatility stocks receive tighter stop levels.
How it works
For long positions, the trailing stop is calculated as:
Highest high over the selected lookback period minus ATR multiplied by the selected multiplier
With the default settings, the calculation is:
22 bar highest high minus 3 times the 14 bar ATR
This creates a stop that hangs below the stock’s recent high, which is why it is called a Chandelier stop.
As the stock makes new highs, the stop can move higher. During normal pullbacks, the stop generally does not move lower while the bullish trend remains intact.
When price closes below the trailing stop, the indicator changes to a bearish state and begins plotting the corresponding stop above price.
Default settings
ATR Length: 14
Price Lookback: 22
ATR Multiplier: 3.0
Automatic Volatility Adjustment: Off by default
These settings are intended as a balanced starting point for swing and position traders using the daily chart and holding trades for several weeks to several months.
Adaptive volatility option
The optional adaptive setting adjusts the ATR multiplier based on ATR as a percentage of the stock price.
When enabled, the indicator gives highly volatile stocks additional room and may tighten the stop for lower volatility stocks. The standard 3 ATR setting remains the default for traders who prefer a simpler and more consistent approach.
Best uses
The indicator is designed for:
• Swing trading
• Position trading
• Trend following
• Managing profitable trades
• Reducing emotional exit decisions
• Monitoring individual stocks or watchlists
It is generally most useful on the daily timeframe.
Alert condition
The script includes an alert condition for a confirmed daily close below the trailing stop.
Recommended PulseWire alert settings:
Condition: Daily Close Below ATR Stop
Interval: 1D
Trigger: Once per bar close
The alert is designed to trigger when the trend first changes from bullish to bearish. It does not repeatedly alert every day while price remains below the stop.
Important considerations
The Trade Control Adaptive ATR Chandelier Stop is a trade management tool, not a complete trading strategy.
Traders should also consider technical support and resistance, entry price, position size, maximum acceptable loss, earnings risk, gap risk, and overall market conditions.
A stock can gap below the plotted stop, particularly around earnings or major news. The indicator does not guarantee execution at the displayed price. Indicator
Volatility Jump DetectorVolatility Jump Detector
This tool marks structurally significant price moves and tells you what kind of move each one was. It is an event detector, not a signal — it does not predict direction. It answers "did something real just happen here, and what was behind it?"
HOW JUMPS ARE DETECTED
Most "big candle" indicators compare a move to an ordinary volatility estimate, which has a circular flaw: a large jump inflates the very volatility measure used to judge it, so the biggest moves look less exceptional than they are.
This uses bipower variation (Barndorff-Nielsen and Shephard; Lee and Mykland), which builds the local volatility estimate from products of adjacent absolute returns. That construction is insensitive to a single large move, and it is computed excluding the current bar — so a jump cannot inflate its own threshold. A move is flagged when it exceeds a chosen multiple of that robust volatility, and the panel reports the exact sigma reading.
TWO INDEPENDENT CONTEXT AXES
INTENSITY — Is the recent jump rate elevated versus its own long-run baseline? Reported as a multiple with the underlying counts always visible, so you can see the sample behind the verdict. Note on method: a Hawkes branching-ratio estimate was implemented first and dropped. At a 4-sigma threshold real data yields only a handful of jumps per few hundred bars, far too few for count-variance statistics — it returned zero on every timeframe tested. A plain rate comparison is what sparse events can actually support, and below a minimum count the reading honestly says "insufficient" rather than printing a fabricated number.
VOLUME — Was the jump backed by participation, or did it slip through a thin book? A large move on heavy volume and the same move on nothing are different events. Auto-disables on instruments without a volume feed.
Optionally link the Risk & Levels Cockpit's exported levels, and jumps that fire through your invalidation level or at the point of control are flagged.
ON THE CHART
Direction-aware triangles mark each jump, colored by the intensity regime at that moment. The most recent jump is labelled with its sigma reading and volume tag. The background tints when jump intensity is elevated. The panel adapts to your chart theme and colors each row by meaning.
WORKS ON ANY MARKET AND TIMEFRAME
All lookbacks are in bars with no session, expiry, or clock anchors. Non-repainting: the robust volatility estimate excludes the current bar, and everything confirms at close.
LIMITATIONS
Not a signal and not investment advice. This marks events and describes them; it does not forecast what follows. An earlier version classified jumps as "ignition" versus "exhaustion" and measured the forward tendency of each — the measured continuation and reversal rates sat at base rate, so that classification was removed rather than kept as decoration. Jump detection depends on the threshold you choose; a lower threshold marks more moves and dilutes significance. Intensity needs a long baseline window because jumps are rare, and reports "insufficient" when the count is too low. Volume confirmation requires a volume feed.
CREDITS
Original implementation. Barndorff-Nielsen and Shephard bipower variation; Lee and Mykland (2008) jump test; jump-rate intensity comparison. Indicator
Triple Barrier Exit with Meta LabelingOverview
Most tools tell you when to enter. This one frames how a trade would be managed — and then keeps an honest record of how that framing actually resolved. It takes a primary entry signal (its own built-in breakout, or any external signal series you point it at), draws a volatility-scaled profit barrier, stop barrier and time barrier around it, watches which is touched first, and feeds every resolved outcome into a live track record. On top sits a meta-label gate: a small online model that learns, from those resolved outcomes, whether to take or skip the next signal.
It is a research and trade-framing study — not a strategy, not a signal service, and not a validated edge.
Why these parts are ONE tool (mashup rationale)
Each layer exists because the one before it leaves a question open:
The triple barrier. A raw entry signal has no definition of success. Profit / stop / time barriers, scaled by current volatility (ATR or an EWMA of returns), turn a signal into a labelled outcome: profit-hit, stop-hit, or timed-out. Widths are regime-asymmetric — the profit barrier widens in trend and tightens in chop — because a fixed frame misprices the same signal in different conditions.
The trend-scanning vertical. A fixed holding time is arbitrary. The time barrier is instead chosen from candidate horizons by the strongest |t-value| of a linear fit — the horizon over which price is actually trending most decisively.
The meta-label gate. Knowing outcomes isn't the same as acting on them. A small online logistic model, trained only on resolved outcomes, scores each new signal and says TAKE or SKIP. It stays disabled until enough trades have resolved, so it never acts on an untrained model.
The honesty layer. Overlapping trades are not independent samples — so wins are recency-decayed and reported with a Wilson 95% lower bound per regime, alongside a reliability table and a Brier score for the meta-gate itself. If the gate isn't calibrated, the panel says so.
Remove any layer and the tool either mislabels the trade, mistimes it, acts on an untested model, or reports a win-rate it hasn't earned.
How it works
A primary signal fires. If the meta-gate passes, the trade is framed: profit = entry ± (PT × regime multiplier × σ), stop = entry ∓ (SL × regime multiplier × σ), and a vertical barrier holdH bars ahead. The frame is drawn as a forward box that recolours green / red / grey on first touch. Same-bar ties resolve stop-first (the conservative assumption). MFE and MAE are tracked live on the open trade. On resolution, the outcome trains the meta-model and updates the per-regime statistics.
How to use it
Read the panel before you trust the frame.
Meta gate — whether the model would take or skip the current signal (stays "warming" until it has enough resolved samples).
Wilson 95% lower — the honest floor of the win-rate in the current regime. If it isn't above 50%, this framing has not demonstrated an edge here.
Meta Brier — below ~0.25 means the gate's probabilities are reasonably calibrated; above it, ignore the gate.
The most useful thing you can do with it: point it at your own entry signal via the external-source input, and see how your signal resolves under a disciplined exit frame. The suggested size is advisory arithmetic (risk ÷ stop distance), not a recommendation. Only one trade is managed at a time — this is a study of the framing, not a portfolio simulator. The dashboard has a Compact layout (default) and a Pro layout (adds the scanned horizon, Brier, reliability tiers, PT/SL/timeout counts, live MFE/MAE and suggested size).
Universal across markets
Entry source, σ source, barrier widths and horizons are all inputs, so it runs on any symbol and timeframe. It needs no volume. Defaults target intraday index futures.
Non-repainting
Entries are taken and outcomes resolved only on confirmed bars, and the meta-model is trained only on resolved outcomes — so no statistic reads its own future and nothing inflates intrabar. The live "next-trade frame" preview is a forward projection at the current bar only, by design.
Originality
The triple barrier, meta-labelling and trend-scanning are published research concepts, credited below. What's assembled here is the specific synthesis: the triple barrier used as a live exit/management frame rather than an offline training pipeline, regime-asymmetric barrier widths, an online meta-gate that trains itself on the chart in front of you, and an honesty panel that reports the Wilson lower bound, the reliability tiers and the gate's own Brier score. Clean-room implementation; no third-party code reused.
Concept credits
Triple-barrier labelling, meta-labelling, trend-scanning, and sample uniqueness / time-decay for non-IID overlapping outcomes — Marcos López de Prado (Advances in Financial Machine Learning). Here the triple barrier is used as an exit/management frame and a labelling substrate, not as a training pipeline.
Wilson score confidence interval — Edwin B. Wilson · Brier score — Glenn W. Brier
Average True Range — J. Welles Wilder · Efficiency Ratio — Perry Kaufman
Inverse-volatility position sizing — standard risk-management practice
Honest limits
Overlapping trades are not independent, which is exactly why wins are decayed and reported with a Wilson lower bound rather than a raw percentage — treat the win-rate as descriptive, not a probability of future results. The meta-model is a small online logistic fit on three features; it can be miscalibrated, which is why its Brier score is shown. All figures are in-sample, with no costs, slippage or spread. Nothing here predicts price.
Disclaimer
Research and educational tool only. Not financial advice, not a recommendation, and no guarantee of results. The position-size output is arithmetic, not advice. Trading carries risk of loss. Test out-of-sample and make your own decisions. The author accepts no liability for any use. Indicator
Risk & Position-Size Calculator : Futures/Prop | Falcon AIStop blowing accounts to oversized positions. This free tool tells you EXACTLY
how many contracts to trade so a stop-out only costs the dollars you decided to
risk — on any futures symbol (MNQ, MES, NQ, ES, MGC, CL and more). It auto-detects
each contract's point value, so the math is always right.
It shows:
• Position size (contracts) for your account + risk %
• Your real $ risk, $/point, and 2R / 3R targets
• Prop-firm guardrails: how many losing trades until you breach your daily-loss
limit or trailing drawdown
• Prior-day high/low for context
Set your account size, risk %, and stop (manual or ATR-based) — it does the rest.
Built by Falcon AI. Educational tool only — not financial advice. Indicator
[Kpt-Ahab] Planned Order Visualizer INDThis Script visualizes planned long or short positions, including an optional existing position size, average entry price, up to three planned entries, a stop-loss level, and an estimated liquidation price. The current position can be treated either as already open or as a new planned entry. In simulation mode, all active entries are included in the calculation immediately, while in live mode only triggered price levels are included. Additional safety settings help prevent historical alerts and can optionally block entry or SL levels that would trigger immediately. The script is designed for planning, visualization, and alerting of planned positions.
**Tips**
* Use **Simulation** mode to preview how all active entries affect the average price before any live alerts are enabled.
* Use **Live** mode only when you want the script to track price-level triggers in real time.
* Keep **Trigger only in realtime** enabled when using alerts, to avoid historical alert triggers after loading the script.
* Use **Block marketable entry limits** and **Block marketable SL** to prevent levels that would trigger immediately.
* Increase the **Reset counter** only when you intentionally want to reset all triggered states and prepare a fresh setup.
* The liquidation price is an estimate for planning purposes and may differ from the exact exchange liquidation price.
This script currently uses a fixed entry structure with `E0` plus `E1`, `E2`, and `E3`. To increase the number of planned entries, duplicate the existing entry blocks and keep the same naming pattern.
For every additional entry, add:
* new input fields for active state, price, and quantity
* new submitted and triggered flags
* average price quantity/value calculations
* price-allowed and price-hit logic
* alert trigger logic
* line and label objects
* table rows if the entry should be shown in the info table Indicator
Indicator
ValidationUtilitiesValidationUtilities Library
🌸 Part of GoemonYae Trading System (GYTS) 🌸
🌸 --------- 1. INTRODUCTION --------- 🌸
💮 What Does This Library Contain?
ValidationUtilities is a centralised validation framework for Pine Script. It replaces scattered, ad-hoc input checks with a single, structured validation pass that catches every misconfiguration before a script begins operating.
The library spans the full validation workflow: framework lifecycle, configuration checks, position sizing guards, and signal completeness verification.
💮 Key Categories
The library contains:
Core Framework : the ValidationFramework UDT and its lifecycle methods (init, collect, report)
Standalone Utilities : bounded-buffer push and division-by-zero guard
Configuration Validation : range, ordering, exclusivity, lookback, source, and timeframe checks
Position Sizing & Risk : order size constraints, progressive risk alerts, allocation distribution, and Martingale safety
Signal & Timing : signal source completeness and cooldown gating
🌸 --------- 2. ADDED VALUE --------- 🌸
💮 Consistent, Readable Error Messages
Every error and warning follows the same Message format. Users see clear, categorised feedback instead of cryptic runtime error strings. A single validation pass surfaces all issues at once, so there is no need to fix one error only to hit the next on re-run.
💮 Single Import, Full Coverage
One import replaces dozens of inline validation blocks. Range checks, allocation constraints, timeframe guards, and position sizing validations are all available immediately.
💮 Errors and Warnings, Separated
Hard/soft boundary separation lets developers enforce critical constraints (errors halt execution via runtime.error() ) whilst still surfacing non-critical suggestions (warnings display as chart labels). The framework handles formatting, counting, and display.
💮 Proven in Production
ValidationUtilities underpins the validation layer of a strategy with an extensive configuration surface (12+ validated parameter groups). The methods have been refined against real misconfiguration scenarios including floating-point allocation sums, multiplier escalation, and unconnected data streams.
🌸 --------- 3. CORE FRAMEWORK --------- 🌸
💮 ValidationFramework (UDT)
The central data structure that collects validation results. It holds two string arrays, errors (critical, halt execution) and warnings (advisory, continue execution), alongside convenience flags has_errors and has_warnings .
Declare once with var , then call init() to reset state before each validation cycle:
var framework = vu.ValidationFramework.new()
framework.init()
💮 init()
Resets the framework: clears both arrays and resets flags to false . Call at the start of each validation cycle.
💮 add_error() and add_warning()
Building blocks for custom validation beyond the built-in methods. Both accept a category and message , formatting them as Message . Use add_error() for constraints that must halt execution and add_warning() for advisory messages.
framework.add_error("Position Sizing", "Order exceeds account equity.")
framework.add_warning("Risk", "Position represents 35% of equity — monitor carefully.")
💮 trigger_errors()
Fires runtime.error() with the first collected error and a count of any remaining. Always call after all validations have run so every misconfiguration is detected in a single pass.
💮 display_warnings()
Renders warnings as orange chart labels (below bar by default). Displays the first warning with a count of additional warnings, then clears state to prevent repetition. Accepts an optional yloc_arg for label placement.
↑ Runtime error dialog showing a categorised validation error with count of additional issues
↑ Warning labels displayed on the chart via display_warnings()
🌸 --------- 4. STANDALONE UTILITIES --------- 🌸
These functions are independent of the ValidationFramework and can be used anywhere.
💮 push_limited()
A FIFO bounded-buffer push: appends a value and evicts the oldest entry when the array exceeds a specified limit. Available for both float and int arrays.
vu.push_limited(price_buffer, close, 50) // Keeps the last 50 closes
💮 safe_denominator()
Returns math.max(value, floor) to guard against division by zero. Default floor is 1e-9 .
ratio = numerator / vu.safe_denominator(denominator)
🌸 --------- 5. CONFIGURATION VALIDATION --------- 🌸
These methods validate user-facing settings before a script begins operating. Each accepts the framework as self and a category string for error grouping. Refer to the source code for full parameter details.
💮 validate_range()
Checks that a value falls within hard bounds (error if violated) and optional soft bounds (warning if outside the optimal range). Supports a value_unit label for message clarity. Returns true if within hard bounds.
💮 validate_exclusive_selection()
Ensures exactly one boolean flag is active among a set of mutually exclusive options. Produces an error listing which options were found active, or that none were selected.
💮 validate_ascending_order()
Verifies that an array of values is in ascending order. Supports strict (default) or non-strict comparison. Skips na values.
💮 validate_minimum_lookback()
Checks that a lookback parameter meets a caller-derived minimum. Accepts an optional fix_hint for the error message. Returns true if met.
💮 validate_source_connected()
Detects when an input.source() has no external indicator connected (it silently defaults to close ). Uses a 2-bar close heuristic. Accepts an is_enabled flag to skip the check when the relevant feature is disabled. Returns true if the source appears connected.
💮 validate_higher_timeframe()
Validates that a user-selected timeframe is sufficiently higher than the chart timeframe. Returns the integer multiplier, useful for scaling lookback periods. Produces an error if below min_multiplier (default 1.0).
🌸 --------- 6. POSITION SIZING & RISK --------- 🌸
These methods guard against position sizing errors and excessive risk exposure. See the source code for parameter details and default thresholds.
💮 validate_order_size_constraints()
Checks a proposed order against account equity and position size limits. Errors if the order exceeds equity or a hard cap; warns if the position exceeds a configurable percentage of equity. Returns true if no errors were added.
💮 validate_multiplied_sizing_risk()
Progressive risk alerting for scripts that scale position sizes with multipliers (Martingale, Anti-Martingale, or any multiplicative sizing). Applies three escalating thresholds:
Warning (default 25%): elevated risk
Error (default 50%): high risk
Critical (default 75%): exceeds safe limits
Also warns when the multiplier itself exceeds a configurable threshold. Returns true if no errors were added.
💮 validate_martingale_settings()
Validates Martingale/Anti-Martingale parameter consistency: multiplier range, streak bounds, and maximum possible escalation. Warns when maximum escalation exceeds 100×.
💮 validate_allocations()
Validates percentage distributions (0–1 scale) for take-profit levels, portfolio weights, or any system that divides a whole into parts. Checks individual allocations and total against 1.0 with floating-point tolerance. Supports both mandatory full allocation and partial allocation.
🌸 --------- 7. SIGNAL & TIMING --------- 🌸
These methods verify signal completeness and enforce cooldown periods. See the source code for parameter details.
💮 validate_signal_configuration()
Completeness check for signal sources. Validates that an enabled signal has a connected primary data stream, a secondary stream (if required), at least one signal mapping, and activity in at least one market regime (when regime filtering is enabled).
💮 validate_timing_cooldown()
Gating check for entry timing. Verifies that enough bars have elapsed since the last relevant event and that a valid entry signal is present. Both conditions produce warnings rather than errors.
🌸 --------- 8. USAGE EXAMPLE --------- 🌸
A typical validation lifecycle: import, initialise, run validations, then trigger errors and display warnings.
import GoemonYae/ValidationUtilities/1 as vu
// Declare once, reset each bar
var framework = vu.ValidationFramework.new()
framework.init()
// Configuration validation
framework.validate_range("Config", "ATR Lookback", i_atr_lookback, 1, 500, 10, 50, "bars")
framework.validate_exclusive_selection("Distance", "TP Mode",
array.from(i_use_pct, i_use_atr, i_use_hl),
array.from("Percentage", "ATR", "High/Low"), "method")
// Allocation validation
framework.validate_allocations("TP Settings", "Take Profit",
array.from(i_tp1_alloc, i_tp2_alloc, i_tp3_alloc),
array.from("TP1", "TP2", "TP3"), true)
// Position sizing guard
framework.validate_order_size_constraints("Sizing",
order_size, close, strategy.equity, max_pos, 50.0)
// Report results
framework.trigger_errors() // Halts if any errors found
framework.display_warnings() // Shows warnings on chart
When all inputs are valid, trigger_errors() does nothing and execution continues; display_warnings() draws no labels. A correctly configured script simply runs with a clean chart.
🌸 --------- 9. PRACTICAL USAGE NOTES --------- 🌸
💮 Errors vs Warnings
Use add_error() for constraints that make the script unsafe or logically broken (missing data streams, impossible parameter combinations, equity-exceeding orders). Use add_warning() for suboptimal but non-dangerous configurations (values outside the recommended range, elevated risk percentages). Errors halt execution; warnings inform via chart labels.
💮 Single-Pass Collection
Always run all validations before calling trigger_errors() . The framework collects every error in a single pass so the user sees the total count of issues.
💮 Integration with Other GYTS Libraries
ValidationUtilities complements the GYTS library ecosystem:
FiltersToolkit : smoothing and signal processing
VolatilityToolkit : volatility estimation and regime detection
ColourUtilities : dynamic colour mapping
MathTransform : mathematical transformations and normalisation
Each library handles its own domain; ValidationUtilities handles the validation layer that sits above them.
💮 Limitations
A few constraints to keep in mind:
The validate_source_connected() heuristic (2-bar close comparison) can produce false positives if a source genuinely tracks price closely. It is a best-effort detection, not a guarantee.
Pine Script libraries cannot import other libraries. So ValidationUtilities is designed for indicators and strategies.
The framework validates configuration state, not runtime state. It catches misconfigurations at the input level; it does not monitor runtime behaviour.
Library
Indicator
Reaction Quality Heat Zones [AGPro Series]Reaction Quality Heat Zones
🧠 Core Idea
Is price reacting with clean quality, or is the zone only producing weak noise and failure pressure?
📌 Overview / What it does
Reaction Quality Heat Zones is a premium PulseWire overlay that evaluates the quality of price reactions around a live reference zone. It studies wick rejection, close location, participation, follow-through, and failed-reaction pressure to determine whether the current reaction area deserves attention.
The script produces a forward-projected heat zone, centered zone label, compact event labels, right-side state tags, and an AGPro-style panel. It is designed to show whether a reaction is clean, weak, absorbing pressure, failing, or producing follow-through.
It does not predict price direction, automate trading, or provide guaranteed entries. It is a visual context tool for reading reaction quality.
🎯 Purpose & Design Philosophy
This script was built because many traders can see a reaction after it happens, but struggle to judge the quality of that reaction in real time.
Reaction Quality Heat Zones helps traders evaluate whether a level, area, or market response is actually meaningful, or whether price is only producing low-quality movement around noise.
The mindset is quality-first: not every bounce, rejection, or reaction deserves the same weight.
⚡ Why This Script Is Different
Most tools mark support, resistance, or candle reactions as isolated events.
This script does NOT treat every wick or bounce as equally important.
Instead, it evaluates reaction quality as a combined structure: wick quality, close behavior, participation, follow-through, and failure pressure are all interpreted together.
⚙️ Methodology
1. Context Detection
The script identifies the dominant reaction side by comparing bullish and bearish reaction quality.
2. Reference Mapping
It builds a heat zone around the most relevant recent reaction boundary.
3. Reaction Evaluation
It scores the zone using wick rejection, close quality, participation, follow-through, and distance from the reaction boundary.
4. Visual Output
It displays a projected heat zone, event labels, state tags, and a structured panel.
🗺️ How to Read the Chart
Zones represent areas where reaction quality is being evaluated.
The centered zone label shows the active reaction heat score.
Labels mark clean reactions, weak reactions, absorption risk, failed reactions, and follow-through events.
Colors represent state context:
• Green = clean or follow-through reaction
• Pink = failed reaction pressure
• Yellow = absorption risk
• Indigo = weak or building reaction
The panel summarizes reaction state, direction, heat score, failure pressure, wick quality, follow-through, and next context.
🚦 Signals & States
• CLEAN REACTION → reaction quality is strong and failure pressure is controlled
• FOLLOW-THROUGH → reaction quality is strong and continuation is visible
• WEAK REACTION → reaction quality is not strong enough yet
• ABSORPTION RISK → quality exists, but failure pressure is also elevated
• FAILED REACTION → failure pressure dominates the reaction area
• REACTION BUILD → no decisive reaction state is confirmed
🔔 Alerts Logic
Alerts trigger when a new clean reaction, follow-through reaction, failed reaction, absorption risk, or weak reaction is detected.
Alerts are attention markers only. They are not trade instructions.
🧩 Confluence Logic
The strongest reaction context appears when wick rejection, close quality, participation, and follow-through align.
The weakest reaction context appears when reaction quality is low and failure pressure increases.
📊 When to Use
• Support and resistance reactions
• Breakout retests
• Range boundary reactions
• Pullback reaction checks
• Intraday and swing market-structure review
⚠️ When NOT to Use
• Very low-liquidity symbols
• Random chop without clear reaction areas
• News-driven spikes
• Charts where spreads or data quality distort candles
🎛️ Key Inputs
• Reaction Lookback → controls the recent window used to build the heat zone
• Follow-Through Length → controls continuation evaluation after reaction
• Heat Threshold → defines how strong a reaction must be to qualify
• Failure Threshold → defines when failure pressure becomes important
• Zone Projection Bars → keeps all zone edges visible for publication screenshots
• Panel and label settings → control readability and layout
🖥️ Interface & Visual Design
The interface is built for fast visual interpretation.
The heat zone carries the main story, while the panel provides structured confirmation. Right-side tags keep the current state readable without burying the candles.
The visual design is intentionally premium, compact, and publication-ready.
🧪 Practical Usage Workflow
1. Read the panel state.
2. Check the active heat zone.
3. Compare heat score with failure pressure.
4. Look for clean reaction or follow-through confirmation.
5. Interpret the result within broader market structure.
🔍 Interpretation Guidelines
High heat with controlled failure pressure suggests a cleaner reaction.
High heat with high failure pressure suggests absorption risk.
Low heat suggests the reaction may not be meaningful yet.
Failed reaction pressure does not guarantee reversal. It shows that the reaction area is losing quality.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an automated trading system.
It does not provide guaranteed buy or sell signals.
It does not replace risk management.
⚠️ Limitations & Transparency
Reaction quality can change quickly.
Different timeframes may show different reaction behavior.
Volatility, liquidity, market sessions, and sudden news can affect how zones behave.
Outputs should always be interpreted with broader market context.
🧠 Market Context Notes
A good reaction is not only a wick.
It also needs close quality, participation, and follow-through. This script is designed to make that difference visible.
🧾 Use Case Examples
When price reacts from a zone with strong wick quality, strong close behavior, and follow-through, the heat score can confirm a cleaner reaction.
When price reacts but failure pressure rises, the zone may be vulnerable.
When price stays inside the zone without quality, the script may show weak reaction or reaction build context.
🧱 System Philosophy
AGPro Series scripts are designed to make complex market context easier to read without reducing the market to simplistic signals.
This script follows that philosophy by focusing on reaction quality instead of generic support or resistance marks.
🔐 Non-Promise Statement
No script can guarantee future price movement.
This tool provides structured context, not certainty.
📉 Risk Disclosure
Trading involves risk.
Users remain responsible for their own decisions, position sizing, and risk management.
This script does not provide financial advice or guaranteed trading outcomes.
📚 Educational Note
Use this script to study how price reacts around important areas and to compare clean reactions with weak or failed reactions across different market conditions.
Indicator
Exhaustion Fuel Gauge [AGPro Series]Exhaustion Fuel Gauge
🧠 Core Idea
Is the current move still powered by real participation, or is the trend running on exhausted fuel?
📌 Overview / What it does
Exhaustion Fuel Gauge is a premium PulseWire overlay that evaluates trend fuel, participation strength, extension pressure, wick reaction, and momentum efficiency to map whether a directional move is still active, fading, or entering exhaustion territory.
The script produces a forward-projected fuel zone, compact state labels, current context tags, and an AGPro-style panel that summarizes the active gauge state. It is designed to help users read whether a move has enough internal fuel to continue or whether the chart is showing signs of weakening participation and exhaustion risk.
It does not predict price direction, automate trades, or provide guaranteed signals. It is a visual decision-support map for market context.
🎯 Purpose & Design Philosophy
This script was built to fill the gap between simple momentum indicators and real chart context. Many tools show whether price is moving fast, but they do not clearly explain whether the move still has fuel or whether the movement is becoming fragile.
Exhaustion Fuel Gauge helps discretionary traders, swing traders, intraday traders, and market-structure readers evaluate the quality of a move before overreacting to a single candle.
The design philosophy is simple: trend continuation should be judged by fuel, participation, efficiency, and reaction quality together.
⚡ Why This Script Is Different
Most tools focus on overbought or oversold readings.
This script does NOT treat exhaustion as a single oscillator value or a generic reversal signal.
Instead, it combines directional persistence, participation strength, range behavior, move efficiency, wick pressure, and extension risk into a clean overlay that explains whether the current move still has usable fuel.
⚙️ Methodology
1. Context Detection
The script identifies the active directional context using recent price movement and trend baseline behavior.
2. Fuel Evaluation
It measures persistence, participation, range expansion, and efficiency to estimate how much usable fuel remains in the move.
3. Exhaustion Risk Mapping
It evaluates extension, fuel fade, wick pressure, and participation fade to estimate whether the move is becoming vulnerable.
4. Visual Output
The script displays a forward-projected fuel zone, event labels, right-side context tags, and a structured AGPro panel.
🗺️ How to Read the Chart
Zones represent the current fuel reference area where the active move should be evaluated.
Labels mark important changes such as fuel activation, fuel fading, exhaustion watch, exhaustion hit, or reset build.
Colors represent state context:
• Green = active fuel
• Pink = exhaustion risk or exhaustion hit
• Yellow = caution / watch state
• Indigo = fading or reset context
The panel summarizes the current gauge state, direction, fuel score, exhaustion risk, participation, extension, and next context.
🚦 Signals & States
• FUEL ACTIVE → directional move still has usable internal fuel
• FUEL FADING → move is still present, but internal support is weakening
• EXHAUSTION WATCH → extension and reaction pressure are elevated
• EXHAUSTION HIT → exhaustion evidence is strong and fuel has weakened
• RESET BUILD → no clean directional fuel is currently confirmed
🔔 Alerts Logic
Alerts trigger when the script detects a new fuel-active state, fuel-fading state, exhaustion-watch state, exhaustion-hit state, or reset-build state.
Alerts are attention markers only. They are not trade instructions and should not be interpreted as guaranteed outcomes.
🧩 Confluence Logic
The strongest exhaustion context appears when extension pressure, participation fade, wick reaction, and weak fuel score align.
The strongest continuation context appears when fuel score remains high while exhaustion risk stays contained.
📊 When to Use
• Trending markets where continuation quality matters
• Extended moves where exhaustion risk needs to be evaluated
• Breakout follow-through analysis
• Swing-trading context review
• Intraday movement quality checks
⚠️ When NOT to Use
• Extremely low-liquidity markets
• Randomly choppy symbols with poor structure
• News spikes where normal participation behavior is distorted
• Very low timeframes with excessive noise
🎛️ Key Inputs
• Trend Length → adjusts the baseline used to define directional context
• Fuel Lookback → controls how many bars are used for fuel evaluation
• Exhaustion Threshold → adjusts how strict exhaustion detection is
• Fuel Fade Threshold → defines when a move is considered fuel-fading
• Zone Projection Bars → keeps the active zone visible for publication screenshots
• Panel and label settings → control visual readability
🖥️ Interface & Visual Design
The interface is built for quick visual interpretation.
The panel provides structured context without dominating the chart. The fuel zone gives the main story visually, while compact labels and right-side tags provide the current state without clutter.
The goal is a premium, publication-ready PulseWire chart.
🧪 Practical Usage Workflow
1. Read the panel state.
2. Check whether fuel is active, fading, or exhausted.
3. Observe the active fuel zone and current right-side tags.
4. Compare exhaustion risk with participation and extension.
5. Use broader market structure before making any decision.
🔍 Interpretation Guidelines
High fuel with low exhaustion risk suggests the move still has internal support.
High exhaustion risk with weak fuel suggests the move may be vulnerable to reaction or reset.
Fuel fading does not mean reversal. It means continuation quality is weakening.
Exhaustion hit does not guarantee a top or bottom. It marks a context that deserves caution.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an automated trading system.
It does not provide guaranteed buy or sell signals.
It does not replace risk management or independent analysis.
⚠️ Limitations & Transparency
The script is rule-based and depends on market conditions.
Different timeframes may produce different readings.
Volatility, liquidity, gaps, and news-driven moves may affect signal quality.
Outputs should always be interpreted with broader market context.
🧠 Market Context Notes
Exhaustion is not only about price distance.
It also depends on whether participation remains strong, whether candles still close efficiently, and whether wick pressure begins to appear against the current direction.
This script is designed to make those conditions easier to read visually.
🧾 Use Case Examples
When price extends strongly but fuel remains high and exhaustion risk is contained, the move may still have continuation quality.
When price extends while participation fades and wick pressure increases, the chart may be entering exhaustion-watch territory.
When exhaustion risk rises while fuel drops, the context becomes more fragile.
🧱 System Philosophy
AGPro Series tools are designed as professional visual maps, not signal machines.
The goal is to make complex market context easier to interpret without reducing it to a simplistic buy or sell label.
🔐 Non-Promise Statement
No script can guarantee future price movement.
This tool provides structured context, not certainty.
📉 Risk Disclosure
Trading involves risk.
Past behavior does not guarantee future results.
Users are responsible for their own decisions, position sizing, and risk management.
This script does not provide financial advice.
📚 Educational Note
Use this script as a learning and analysis tool to better understand momentum quality, trend fuel, and exhaustion behavior across different market conditions.
Indicator
Acceptance Failure Path Map [AGPro Series]Acceptance Failure Path Map
🧠 Core Idea
Did price truly accept beyond a market boundary, or did that acceptance fail and create a new reaction path?
📌 Overview / What it does
Acceptance Failure Path Map is a market-structure visualization tool designed to study acceptance, failed acceptance, reclaim attempts, and continuation behavior around a defined reference range.
The script maps an acceptance band, detects whether price holds above or below that band, and highlights when accepted price fails back through the boundary. It produces compact labels, a centered path zone, right-side state tags, and an AG Pro panel that summarizes the current acceptance context.
It does not predict price direction, automate decisions, or claim that any acceptance event must continue. Its purpose is to make acceptance quality easier to read.
🎯 Purpose & Design Philosophy
This script was built for traders who want to understand whether a move is being accepted by the market or rejected after a temporary push beyond structure.
Many breakout tools mark only the breakout event. This script focuses on what happens after the breakout: acceptance, failure, reclaim pressure, and continuation risk.
The design supports a patient, context-first workflow where the trader reads the path of price around a boundary instead of reacting to a single candle.
⚡ Why This Script Is Different
Most tools focus on breakout signals, support and resistance touches, or simple range breaks.
This script does NOT treat every break as meaningful acceptance.
Instead, it builds a path map around acceptance quality, failure timing, reclaim behavior, and current risk state. The result is a cleaner view of whether price is holding acceptance or losing it.
⚙️ Methodology
1. Context Detection
The script builds a reference range from recent market structure and applies an ATR-based buffer to reduce noise.
2. Reference Mapping
It defines upper and lower acceptance boundaries and tracks whether price closes beyond them for the required number of bars.
3. Reaction Evaluation
After acceptance appears, the script monitors whether price fails back through the boundary, attempts reclaim, or holds continuation.
4. Visual Output
The chart displays an acceptance path zone, event labels, right-side state tags, and a panel summarizing the current condition.
🗺️ How to Read the Chart
Zones show the current acceptance path area around the active boundary.
Labels highlight acceptance above, acceptance below, acceptance failure, reclaim tests, and held acceptance.
Colors separate bullish acceptance, bearish acceptance, neutral failure risk, and reclaim context.
The panel shows the current path state, acceptance side, failure risk, path quality, reference range, active boundary, and next context.
🚦 Signals & States
• ACCEPT ABOVE → Price has accepted above the reference boundary.
• ACCEPT BELOW → Price has accepted below the reference boundary.
• ACCEPT FAIL → Accepted price failed back through the boundary within the failure window.
• RECLAIM TEST → Price is testing reclaim after a failed acceptance event.
• ACCEPT HELD → Acceptance remained valid after the failure window.
🔔 Alerts Logic
Alerts trigger when the script detects acceptance above, acceptance below, acceptance failure, or reclaim testing.
These alerts are attention markers. They are not trade instructions, entry signals, or guaranteed outcomes.
🧩 Confluence Logic
The context becomes stronger when acceptance quality, distance from the reference range, participation, and follow-through direction align.
If acceptance appears without follow-through or quickly returns through the boundary, the failure context becomes more important.
📊 When to Use
• After range breaks
• Around support and resistance transitions
• During breakout retests
• When price is attempting to hold above or below a major boundary
• When evaluating whether market structure is accepted or rejected
⚠️ When NOT to Use
• Extremely illiquid markets
• Very noisy low-timeframe candles
• News-driven spikes with unstable spreads
• Markets with no meaningful reference range
• Situations where a single indicator is being used without broader context
🎛️ Key Inputs
• Reference Range Length → controls how much structure is used to build the acceptance boundary.
• Acceptance Bars → controls how many closes are required before acceptance is recognized.
• Failure Window → controls how quickly accepted price must fail back through the boundary.
• Boundary Buffer ATR → adjusts the buffer around the reference range.
• Label and Panel Font Size → adjust chart readability.
• Visible Band Bars and Band Projection Bars → control how the acceptance zone appears on the chart.
🖥️ Interface & Visual Design
The interface is designed for a premium, clean chart view.
The panel provides the current summary. The acceptance zone carries the main story. Labels are compact and spaced to avoid hiding candles.
The visual hierarchy is intentionally simple: zone first, current state second, event labels third.
🧪 Practical Usage Workflow
1. Read the AG Pro panel to identify the current path state.
2. Check whether price is above, below, or inside the acceptance path zone.
3. Review recent labels to understand whether acceptance held, failed, or reclaimed.
4. Compare the current failure risk and path quality with broader market context.
5. Use alerts only as attention markers for further review.
🔍 Interpretation Guidelines
Acceptance is stronger when price remains outside the boundary with follow-through.
Acceptance failure is more meaningful when price quickly returns through the boundary after appearing accepted.
Reclaim tests should be interpreted as context changes, not automatic reversal signals.
Held acceptance suggests the market is continuing to respect the accepted side, but it still requires confirmation from broader structure.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an automated trading system.
It does not provide guaranteed buy or sell signals.
It does not replace risk management, market context, or independent analysis.
⚠️ Limitations & Transparency
Acceptance behavior can look different across timeframes.
High volatility can create temporary false readings.
Low-liquidity markets may produce unstable boundary behavior.
The script is rule-based and depends on the selected settings, symbol behavior, and chart timeframe.
🧠 Market Context Notes
Acceptance and failure are closely related to market structure, liquidity reaction, and participant commitment.
When price breaks a boundary but cannot hold it, the failed side may become the more important context.
When price accepts and holds, the market may be showing stronger directional commitment.
🧾 Use Case Examples
When price accepts above a range and holds beyond the failure window, the chart may show an ACCEPT HELD context.
When price accepts above a boundary but quickly closes back below it, the script may mark ACCEPT FAIL.
When price returns back toward a failed boundary, the script may show a RECLAIM TEST state.
🧱 System Philosophy
AGPro Series tools are built to visualize market context without turning analysis into prediction.
The goal is to make structure, risk, and reaction quality easier to observe in real time.
🔐 Non-Promise Statement
No script can guarantee market direction, timing, or outcome.
This tool provides structured visual context only.
📉 Risk Disclosure
Trading involves risk.
Users are responsible for their own decisions, risk management, and position sizing.
This script does not provide financial advice or guaranteed trading results.
📚 Educational Note
Use this script as a learning and analysis tool for studying acceptance, failed acceptance, reclaim pressure, and continuation behavior around market boundaries.
Indicator
Candle Intent Map [AGPro Series]Candle Intent Map
🧠 Core Idea
Does this candle show initiative, absorption, rejection, indecision, or a real shift in intent?
📌 Overview / What it does
Candle Intent Map is a candle behavior and market reaction tool designed to read the internal message of price candles beyond simple bullish or bearish color.
The script evaluates body pressure, wick reaction, close location, volume context, short follow-through, and recent intent changes to classify whether the market is showing initiative, absorption, rejection, indecision, or an intent shift.
It produces compact labels, a visible intent pressure zone, right-side context tags, and a clean AG Pro panel. It does not predict price, automate decisions, or promise that a candle pattern will continue.
🎯 Purpose & Design Philosophy
This script was built because many candlestick tools stop at basic pattern recognition.
A candle is not only a shape. It is a relationship between body commitment, wick reaction, volume participation, close location, and what happens immediately after that candle forms.
Candle Intent Map helps traders who want to read candle quality, initiative pressure, reaction zones, and follow-through context without turning the chart into a crowded pattern scanner.
⚡ Why This Script Is Different
Most candle tools focus on named formations such as engulfing candles, pin bars, doji candles, or simple color changes.
This script does NOT treat every candle pattern as an automatic signal.
Instead, it studies whether the candle has enough internal pressure, reaction quality, volume context, and follow-through to deserve attention.
The goal is not to label more candles. The goal is to label the candles that tell a clearer market story.
⚙️ Methodology
1. Context Detection
The script measures body-to-range ratio, upper wick pressure, lower wick pressure, close location, and relative volume participation.
2. Intent Classification
Candles are classified into initiative, absorption, rejection, indecision, or intent shift conditions based on body pressure, wick behavior, and directional commitment.
3. Reaction Evaluation
The script builds a reaction-quality score using body strength, wick reaction, close placement, volume context, and short follow-through behavior.
4. Visual Output
The strongest current candle intent context is mapped as a visible intent zone, compact event labels, right-side state tags, and a structured AG Pro panel.
🗺️ How to Read the Chart
Zones represent the most recent candle intent pressure area.
Labels show important candle intent events such as bullish intent, bearish intent, absorption, rejection, indecision, or intent shift.
Colors separate constructive pressure, defensive pressure, neutral reaction, and absorption-style behavior.
The panel summarizes current intent, direction, body pressure, wick reaction, follow-through, quality score, and next context.
🚦 Signals & States
• BULL INTENT → bullish body pressure with meaningful close location and participation
• BEAR INTENT → bearish body pressure with meaningful close location and participation
• ABSORPTION → strong reaction behavior with compressed body and meaningful volume
• LOWER REJECT → lower wick reaction suggesting downside rejection
• UPPER REJECT → upper wick reaction suggesting upside rejection
• INDECISION → low body commitment with balanced wick behavior
• INTENT SHIFT → recent candle intent changes direction with enough pressure to matter
🔔 Alerts Logic
Alerts trigger when the script detects bullish candle intent, bearish candle intent, candle absorption, or candle intent shift.
These alerts are attention markers only. They highlight a candle context that may deserve review, not a trade instruction.
🧩 Confluence Logic
The strongest context appears when candle body pressure, wick reaction, close location, volume participation, and follow-through point in the same direction.
When these components align, the candle intent quality score becomes stronger.
📊 When to Use
• During active trend continuation phases
• Around reaction zones and pullback areas
• Near support, resistance, VWAP, or liquidity references
• When evaluating whether a candle has real participation behind it
• When comparing initiative candles against absorption or rejection candles
⚠️ When NOT to Use
• Extremely illiquid markets
• Very noisy low-timeframe environments
• News-driven candles with abnormal spreads
• Symbols with unreliable volume data
• Situations where broader market context is ignored
🎛️ Key Inputs
• Volume Context Length → controls the relative volume comparison window
• Follow-Through Length → controls how short-term continuation is measured
• Initiative Body Ratio → changes how strict the initiative candle filter is
• Reaction Wick Ratio → changes how strict wick-based rejection and absorption filters are
• Visible Zone Bars → controls how much of the recent chart the intent zone covers
• Label and Panel Font Size → controls visual readability
🖥️ Interface & Visual Design
The interface is designed to stay clean, readable, and publication-friendly.
The chart focuses on one main intent zone, compact event labels, right-side context tags, and a structured panel.
The visual hierarchy is intentional: zone first, current state second, historical intent events third.
🧪 Practical Usage Workflow
1. Read the panel to understand the current candle intent state
2. Check the intent zone and its position relative to price
3. Review recent labels to understand whether initiative, absorption, or rejection has dominated
4. Compare the quality score with current follow-through
5. Interpret the output inside broader market context
🔍 Interpretation Guidelines
A strong intent label does not mean price must continue.
A rejection label does not mean reversal is guaranteed.
An absorption label means the candle structure showed reaction and participation, but confirmation still depends on the following market behavior.
The best interpretation comes from combining candle intent with structure, liquidity, volatility, and timeframe context.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an auto-trading system.
It does not provide guaranteed buy or sell signals.
It does not replace risk management or independent analysis.
⚠️ Limitations & Transparency
Candlestick interpretation changes across timeframes.
Volume quality may differ between markets and exchanges.
Fast volatility expansion can make recent candle intent less stable.
Low-liquidity conditions may create misleading wick or body readings.
Users should always interpret outputs within broader market context.
🧠 Market Context Notes
Candle intent is most useful when combined with structure, liquidity, trend quality, volatility, and acceptance behavior.
One candle rarely tells the whole story. The value comes from understanding whether candle pressure is supported or rejected by what comes next.
🧾 Use Case Examples
When price reaches a known support area and the script prints a lower rejection label with improving quality, the trader can study whether downside pressure is being rejected.
When a strong body candle prints with high quality and follow-through, the trader can evaluate whether initiative pressure is entering the market.
When absorption appears inside a range, the trader can watch whether trapped pressure develops or fades.
🧱 System Philosophy
Candle Intent Map is part of the AGPro Series approach: clean visual tools that focus on market context, reaction quality, and decision support rather than prediction claims.
The script is designed to make candle behavior easier to read while keeping the trader responsible for interpretation.
🔐 Non-Promise Statement
No script can know the future.
No candle label guarantees continuation or reversal.
This tool provides structured visual context only.
📉 Risk Disclosure
Trading involves risk.
Market conditions can change quickly.
All decisions remain the responsibility of the user.
This script does not provide financial advice or guaranteed trading outcomes.
📚 Educational Note
Use this script as an educational and analytical companion for studying candle behavior, reaction quality, and short-term intent context.
Indicator
VWAP Control Shift Map [AGPro Series]VWAP Control Shift Map
🧠 Core Idea
Has VWAP control shifted from mean reversion to directional acceptance?
📌 Overview / What it does
VWAP Control Shift Map is a VWAP control and acceptance visualization tool built to identify when price is balanced around value, accepted above control, accepted below control, or rejected back into the VWAP band.
The script builds a rolling volume-weighted control line, maps a VWAP control band, labels acceptance and rejection events, and summarizes the current VWAP state in a compact AG Pro panel.
This script does not predict future price direction, automate trades, or provide guaranteed buy/sell signals. It is a structured decision-support map for VWAP control, acceptance quality, mean-reversion risk, and shift context.
🎯 Purpose & Design Philosophy
VWAP is one of the most watched value references across intraday and swing trading contexts.
The problem is that price can cross VWAP many times without meaningful control transfer. This script was built to separate casual VWAP interaction from stronger acceptance, rejection, and reversion behavior.
The design philosophy is to make VWAP context visually readable: where control sits, which side is accepted, whether reversion risk is rising, and whether the shift has quality.
⚡ Why This Script Is Different
Most VWAP tools plot a line, add bands, and leave interpretation entirely to the user.
This script does NOT simply mark every VWAP touch as important and does NOT treat every cross as a trend signal.
Instead, it frames VWAP as a control zone: acceptance above, acceptance below, rejection back into value, and mean-reversion risk are all organized into one visual map.
⚙️ Methodology
1. VWAP Control Detection
The script calculates a rolling volume-weighted control line using price and volume over the selected control window.
2. Control Band Mapping
It builds a volatility-adjusted band around VWAP to represent the current value-control area.
3. Acceptance Evaluation
Consecutive closes outside the band are used to identify directional acceptance.
4. Rejection Evaluation
If price returns into the band after a shift, the script marks VWAP rejection behavior.
5. Visual Output
The chart displays the VWAP control line, bordered control zone, centered band label, event labels, right-side state tags, and AG Pro panel.
🗺️ How to Read the Chart
The VWAP control line represents the rolling volume-weighted value reference.
The control band represents the active VWAP acceptance area.
Labels mark acceptance, rejection, and mean-reversion events.
Right-side tags show the current control state and shift quality.
The panel summarizes VWAP control, acceptance state, control side, reversion risk, shift quality, control band, and next context.
🚦 Signals & States
• VWAP BALANCE → price has not established a clear accepted side
• ACCEPT ABOVE → price has accepted above the VWAP control band
• ACCEPT BELOW → price has accepted below the VWAP control band
• VWAP REJECTION → a control shift returned back into the band
• REVERSION RISK → price is back inside the band after a directional control state
🔔 Alerts Logic
VWAP Control Shift Up alert triggers when price accepts above the VWAP control band.
VWAP Control Shift Down alert triggers when price accepts below the VWAP control band.
VWAP Rejection alert triggers when price returns back into the band after a control shift.
Alerts are attention markers. They are not trade instructions.
🧩 Confluence Logic
The context becomes stronger when acceptance direction, VWAP slope, distance from VWAP, and candle body pressure align.
The context becomes weaker when price quickly returns into the control band after an attempted shift.
📊 When to Use
• VWAP-based intraday analysis
• Swing charts where volume-weighted value remains relevant
• Mean-reversion versus directional acceptance decisions
• Markets with liquid volume and clean price structure
• Trend continuation or failed acceptance review
⚠️ When NOT to Use
• Very illiquid symbols
• Markets with unreliable volume
• Extremely noisy low-timeframe charts
• News shock environments where VWAP control changes abruptly
• Any context where a single indicator is being used without broader structure
🎛️ Key Inputs
• VWAP Control Length → controls the rolling volume-weighted control window
• Band Volatility Length → controls how the band width is calculated
• Control Band Multiplier → adjusts VWAP control band width
• Acceptance Bars → defines how many closes are needed for acceptance
• Rejection Window → controls failed-shift timing
• Visual settings → control the panel, zone, labels, font sizes, and projection
🖥️ Interface & Visual Design
The interface is designed for clean, premium chart reading.
The VWAP band uses visible four-edge zone boundaries so the control area remains clear in both editor and published PulseWire views.
The panel uses the AG Pro merged blue header standard and keeps the current context readable without covering the main chart.
🧪 Practical Usage Workflow
1. Read the panel state.
2. Check whether price is inside, above, or below the VWAP control band.
3. Review acceptance or rejection labels.
4. Compare shift quality with reversion risk.
5. Use broader market structure before making any decision.
🔍 Interpretation Guidelines
VWAP control is not a prediction.
Acceptance shows where price has spent enough time outside the control band to suggest directional control.
Rejection shows that the attempted control shift returned back toward value.
Mean-reversion risk increases when price moves back into the VWAP control area after directional acceptance.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an auto-trading system.
It does not guarantee profitable trades.
It does not replace risk management or independent analysis.
⚠️ Limitations & Transparency
VWAP behavior can vary by timeframe, market session, liquidity, and volume quality.
Rolling VWAP control may differ from exchange-session VWAP or anchored VWAP tools.
Extreme volatility can temporarily reduce the usefulness of control-band interpretation.
Outputs should always be interpreted within broader market context.
🧠 Market Context Notes
VWAP often works as a value reference, but value can shift when acceptance becomes persistent.
A clean control shift is stronger when price accepts outside the band while VWAP slope supports the move.
A weak shift often returns back into the band and becomes a rejection or mean-reversion context.
🧾 Use Case Examples
When price accepts above the VWAP control band with strong shift quality, the chart may be showing directional control above value.
When price accepts below the band and VWAP turns down, the control context may favor downside acceptance.
When price quickly returns into the band after acceptance, VWAP rejection risk becomes more important.
🧱 System Philosophy
AGPro Series tools are built to convert complex market behavior into visual decision maps.
The goal is not certainty. The goal is structured context, cleaner interpretation, and better chart discipline.
🔐 Non-Promise Statement
No script can know the future.
No signal is certain.
No visual state should be treated as a guaranteed outcome.
📉 Risk Disclosure
Trading involves risk.
Markets can move unexpectedly.
Users are responsible for their own decisions, risk management, and trade execution.
This script does not provide financial advice.
📚 Educational Note
This tool is intended for educational and analytical use. It can help traders study VWAP control, acceptance shifts, rejection behavior, and mean-reversion risk.
Indicator
Volatility Compression Release Map [AGPro Series]Volatility Compression Release Map
🧠 Core Idea
Is the market quietly building expansion energy, or has the release already failed back into the shelf?
📌 Overview / What it does
Volatility Compression Release Map is a volatility regime and compression shelf visualization tool built to identify quiet range contraction, release attempts, fake releases, and expansion quality.
The script maps a projected compression shelf when volatility rank and range size contract together. It then tracks whether price releases away from that shelf, returns back inside it, or continues to hold expansion pressure.
This script does not predict future price direction, automate trades, or produce guaranteed buy/sell signals. It is designed as a structured chart-reading layer for volatility compression, release quality, and contextual risk.
🎯 Purpose & Design Philosophy
The script was built for traders who care about the transition between quiet markets and expansion phases.
Many charts look calm before movement starts. The challenge is not simply seeing a tight range, but understanding whether that range is still building energy, whether the release is active, or whether the move has already failed back into the shelf.
The design philosophy is simple: reduce volatility noise into a readable map, preserve the important shelf story, and make the current regime understandable at first glance.
⚡ Why This Script Is Different
Most tools focus on breakout arrows, squeeze dots, or raw volatility bands.
This script does NOT treat every contraction as an immediate trade signal and does NOT frame every expansion candle as confirmation.
Instead, it builds a full compression-to-release map: the shelf, volatility rank, range size, release direction, fake-release risk, quality score, right-side state labels, and a compact AG Pro panel all work together.
⚙️ Methodology
1. Context Detection
The script evaluates ATR rank, recent range size, and whether price is still inside a quiet shelf.
2. Shelf Mapping
When compression conditions align, the active range is stored and projected forward as a compression shelf.
3. Release Evaluation
The script checks whether price leaves the shelf with enough candle body expansion to qualify as a release attempt.
4. Failure Tracking
If price quickly returns into the shelf during the fake-release window, the state changes to fake release.
5. Visual Output
The chart displays a projected shelf, dotted rails, a centered shelf-quality label, event labels, right-side state tags, and a compact AG Pro panel.
🗺️ How to Read the Chart
Zones represent the active compression shelf.
The shelf label shows the current shelf quality score using a compact `SHELF | Q` format.
Green/teal visual states generally indicate constructive expansion or defended release behavior.
Pink visual states highlight failed release or adverse volatility behavior.
Indigo/accent visuals represent compression and neutral shelf structure.
The panel summarizes compression state, release direction, volatility rank, range size, quality score, shelf range, and next context.
🚦 Signals & States
• COMPRESSION BUILD → a quiet shelf is forming and volatility is compressed
• RELEASE ACTIVE → price has moved away from the shelf with sufficient body expansion
• FAKE RELEASE → price returned back into the shelf after a release attempt
• SHELF WATCH → a shelf exists but the market has not produced a clean active release
• WAIT COMPRESSION → no valid compression shelf is currently active
🔔 Alerts Logic
Compression Build alert triggers when a new volatility compression shelf is detected.
Compression Release alert triggers when price releases from the active shelf with enough candle body expansion.
Fake Release alert triggers when price returns back into the shelf within the defined fake-release window.
Alerts are attention markers. They are not trade instructions.
🧩 Confluence Logic
The context becomes stronger when low volatility rank, compact range size, a visible shelf, and a strong release candle align.
The context becomes weaker when price fails back into the shelf shortly after release.
📊 When to Use
• Before potential expansion phases
• During quiet range compression
• Around breakout preparation zones
• When evaluating whether a move is expanding or failing
• On liquid markets where volatility structure is meaningful
⚠️ When NOT to Use
• Extremely illiquid symbols
• Very noisy low-timeframe charts
• News shock environments where volatility structure changes suddenly
• Markets with unreliable volume or large gaps
• Situations where a single indicator is being used without broader context
🎛️ Key Inputs
• Compression Lookback → controls the range window used to detect the shelf
• Volatility Rank Lookback → controls how ATR rank is measured
• Compression Rank Max → changes how selective compression detection is
• Range ATR Max → limits how wide a valid shelf can be
• Release Body ATR Min → defines how strong a release candle must be
• Fake Release Window → controls how quickly a release failure is detected
• Visual settings → control shelf projection, labels, panel, theme, and font sizes
🖥️ Interface & Visual Design
The interface is designed to look clean, premium, and publication-ready.
The shelf is the main visual anchor. Event labels are intentionally limited so the chart does not become crowded.
The AG Pro panel uses a merged blue header row and summarizes the state without covering the main chart story.
🧪 Practical Usage Workflow
1. Read the panel state.
2. Locate the active compression shelf.
3. Check whether price is inside, releasing, or failing back into the shelf.
4. Compare the quality score with the visual structure.
5. Use broader market context before making any decision.
🔍 Interpretation Guidelines
Compression is not direction.
A shelf shows where volatility has contracted.
A release shows that price moved away from the shelf with expansion pressure.
A fake release shows that the market rejected the expansion and returned to the compression area.
The strongest interpretations come from combining the shelf, state, quality score, and surrounding market structure.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an auto-trading system.
It does not guarantee profitable trades.
It does not replace risk management or independent analysis.
⚠️ Limitations & Transparency
Timeframe differences can change how compression and release behavior appears.
High volatility news events may reduce the usefulness of shelf-based interpretation.
Low-liquidity markets can produce misleading shelves and sudden false releases.
The script is rule-based and should always be interpreted within broader market context.
🧠 Market Context Notes
Volatility often contracts before expansion, but compression alone does not define direction.
The shelf helps identify where the market has stored recent range energy.
Release quality helps separate stronger expansion attempts from weak movement outside the range.
🧾 Use Case Examples
When price remains inside a shelf while volatility rank is low, the market may still be building energy.
When price leaves the shelf with strong body expansion, the script marks release behavior.
When price returns into the shelf quickly, the script flags a fake-release context.
🧱 System Philosophy
AGPro Series tools are built to turn complex market behavior into structured visual maps.
The goal is not to simplify markets into certainty, but to make important context easier to read.
🔐 Non-Promise Statement
No script can know the future.
No signal is certain.
No visual state should be treated as a guaranteed outcome.
📉 Risk Disclosure
Trading involves risk.
Markets can move unexpectedly.
Users are responsible for their own decisions, risk management, and trade execution.
This script does not provide financial advice.
📚 Educational Note
This tool is intended for educational and analytical use. It can help traders study volatility compression, release behavior, fake-release risk, and shelf-based market context.
Indicator
ATR Volatility Regime [NovaLens]Volatility regime tool built to separate two things ATR alone cannot tell you apart: where volatility currently sits in its own rolling history, and which direction the regime is rotating. Adds a velocity-gated release event on top, so the indicator flags fast coiled-spring releases on the confirmed bar - and refuses to fire on the slow leaks that only look like one.
Most volatility tools collapse one axis. A raw ATR plot tells you the bar range and nothing about whether that range is rare. A percentile-rank histogram tells you the rank but not whether vol is loading or unloading. ATR Volatility Regime separates the two by design:
Tier tracks where volatility sits in its own rolling history (Compression / Quiet / Normal / Elevated).
Phase tracks where volatility is rotating (Rising / Topping / Falling / Bottoming).
A Compression reading is not a breakout signal. It is the market saying "vol is loaded." Whether it actually releases depends on the next move. When a sustained compression actually breaks above mid-rank within a 5-bar velocity window, the indicator prints a Release diamond and pulses the pane background. Slow leaks that drift through Quiet for more than 5 bars are canceled, not reported. That single gate is what separates a real coiled-spring release from a sideways drift.
════════════════════════════════════════════
◉ HOW IT WORKS
The vol input. Wilder ATR over the chosen length, expressed as a percentage of close so the read is comparable across price levels and instruments. Mathematically guarded to stay clean across historical data gaps and unusual price series.
The percentile rank. The current ATR% is ranked against its own rolling lookback window (100 / 200 / 300 bars by Horizon). This is an asset-calibrated percentile - "P75 on BTC" means "vol higher than 75% of the last 200 BTC readings," not a market-wide cutoff. The same indicator works across SPY, BTC, EURUSD, and XAU without retuning. The raw rank drives the state engine; an EMA-smoothed copy drives the visual line so the plot reads calm without numbing event detection. Warm-up is honest: until the lookback fills, the panel shows "Warming up" and refuses to assign a tier. NA never collapses to a fake Normal.
The tier model. Four tiers cut on rawRank (P25, P50, P75) with asymmetric hysteresis: 1 confirmed bar to step up (so a vol breakout is not missed), 3 confirmed bars to step down (so a tier change only confirms when vol has actually died). The ribbon fill and oscillator line both color by tier. Extreme is a signal class, not a tier; it would flicker on and off at the P90 boundary if we colored the ribbon by it.
The phase model. Four phases (Rising / Topping / Falling / Bottoming) read off the rawRank slope. Slow rotations need 2 bars of confirmation to flip; violent moves with |delta rank| > 15 bypass the confirm and flip immediately. Peak and trough detection is plateau-aware: a strict ( greater-than on both sides) check missed the patterns where ATR percentile pins at 100 for multiple bars, so the algorithm uses greater-or-equal on the left side and greater-than on the right.
The events. Three signature events, each with its own gating:
Compression Release : velocity-gated. The Compression tier must run at least 10 bars to load the spring; on exit, rawRank must reach the mid (>= 50) within a 5-bar window. Slow leaks that drift through Quiet for more than 5 bars are canceled. Re-entering Compression also cancels the pending episode.
Extreme Touch : rawRank peaks at >= 90. Re-arm runs through a three-valve cascade (rank drop to <= 75, a higher pivot with a +2 rank headroom so a 98 peak after a 97 cannot re-fire, or 2x lookback time decay) so the same Extreme arc cannot duplicate-fire, but a genuinely higher pivot in the same arc still counts.
Cooling : armed when an Extreme fires; fires on the first confirmed bar after where rawRank falls below 75 within a 10-bar window. Disarms on fire or when the window expires. The armed-latch architecture means fast drops out of an Extreme are tracked after the Extreme event arms Cooling, instead of relying on a single fragile cross check that would miss the drop if the threshold was already crossed on the Extreme bar itself.
The Playbook Lens. Pure interpretation layer. Engine, percentile, tier, phase, and objective events are identical across lenses. The Lens recolors three visual surfaces only: the panel Playbook row text and tone, the Playbook Heatmap Strip at y = -5, and an optional Tint Price Candles by Playbook Fit overlay. Switching the Lens dropdown answers a different question against the same volatility truth: "does this regime align with the workflow I am running?" - context, never a directive.
════════════════════════════════════════════
◈ HOW TO READ IT
The pane shows the smoothed percentile rank line wrapped in a tier-colored ribbon with a Volatility Glow halo that breathes wider in the loaded zones (Compression and Extreme) and tightens in Normal. Threshold lines mark P25, P50, P75, and P90.
Deep blue (Compression): rawRank in [0, 25). Loaded spring.
Light blue (Quiet): rawRank in [25, 50). Below median, not stretched.
Gray (Normal): rawRank in [50, 75). Typical bar ranges.
Orange (Elevated): rawRank in . High vol relative to recent history.
Red (Extreme): event color, not a tier. Drives Extreme Touch markers.
Teal (Release): event color, not a tier. Drives Compression Release markers.
Markers, in order of conviction:
Compression Release (diamond on the line, Release color, with a matching pane background pulse): a >= 10 bar compression run resolved into Normal+ within 5 bars. Non-directional by design - a volatility state change, not a price direction call.
Extreme Touch (small circle anchored to the actual peak bar, Extreme color): rawRank just peaked at or above the 90th percentile of its rolling history. Reads as topping pressure of vol, not a directional reversal call.
Cooling (panel-only event, no chart marker): the first confirmed bar after an Extreme where rawRank fell back below 75 within a 10-bar window. Surfaces in the Last Event row and the Cooling alert.
The info panel synthesizes six rows: Volatility (tier + P-Score), Flow (phase), Age (bars in tier + the per-tier duration percentile so a 200-bar Quiet stretch is compared against historical Quiet stretches, not Elevated), Last Event / Context (state-based decay, no fixed timer), ATR Range (current bar range as % of price, with absolute price-unit ATR in the row tooltip), and Playbook (the Lens context read).
The Last Event row uses state-based decay , not an arbitrary 10-bar timer. A Compression Release stays visible while phase is Rising or tier is Normal+. An Extreme Touch stays visible while tier is Elevated. A Cooling read stays visible while tier is Normal or Elevated. When the event's regime context expires, the row returns to Context and summarizes the current regime instead of resizing or disappearing.
════════════════════════════════════════════
✦ HOW WE USE IT: THE COILED-SPRING ARC
This is the arc the indicator is built to catch - not the only path. Many compressions resolve sideways without a confirmed release, and the velocity gate is what filters those out.
A common pattern on a liquid index or crypto chart, Swing profile (default), Neutral lens: the line drops into Compression and parks there for 15-30 bars. The ribbon turns deep blue, the Glow widens, and the panel Age row may read something like "Mature · 22 bars" or "Extended · 22 bars" - meaning the current run has already lasted longer than most recent Compression stretches on this market. The spring is loaded.
The full arc reads in four panel updates:
Release. rawRank reaches 50+ within the 5-bar velocity window after exiting Compression. A Release diamond prints on the line, the pane background pulses teal for one bar, and the Last Event row reads "Compression Release".
Run. Within a few bars the tier transitions through Normal into Elevated, the phase row flips Rising, and the smoothed line climbs toward the upper distribution.
Touch. If the move keeps loading, rawRank peaks at 92-98 and an Extreme Touch circle prints on the peak bar - the smoothed line is now in the upper edge of its own rolling distribution. The Last Event row updates to "Extreme Touch".
Unwind. Within 10 bars rawRank falls below 75. Cooling fires and the Last Event row updates again.
The Playbook Lens reframes the same arc without changing a number. Flip to Breakout: the Heatmap Strip lights teal during the release window (favorable) and dims toward red as the move stretches into Extreme (less favorable). Flip to Mean Reversion: the strip stays red through the release (vol is the wrong direction for fading) and only lights teal when Cooling confirms and tier drifts back through Normal toward Quiet. Flip to Risk Control: Compression marks calmer bar-range context, Elevated and Extreme mark the wider-bar context. Same volatility truth, different playbook fit. The engine is identical across lenses; only the interpretation layer changes.
════════════════════════════════════════════
✦ OTHER APPLICATIONS
Breakout context : Compression Release diamonds after a loaded quiet regime, optionally combined with the Heatmap Strip reading favorable under the Breakout lens
Trend context : Rising Elevated or Rising Normal volatility as movement context for an external trend plan
Mean-reversion context : quieter or cooling regimes that may be more suitable for contained-range workflows
Volatility risk overlay : Elevated and Extreme states as wider-bar context when reviewing size, stops, or trade frequency
Vol regime classifier : use the Volatility row + Flow row in the panel as a top-down filter for any external trade plan, independent of the Lens
Alert-driven workflow : subscribe to Compression Release + Extreme Touch + Cooling and check the chart only when the volatility regime actually changes, not every bar
════════════════════════════════════════════
⚙ GETTING STARTED
ATR Volatility Regime ships with three pre-tuned Horizon profiles plus a Custom override. Pick a horizon and start reading the regime:
Intraday : ATR 14, lookback 100, smoothing 3. Faster events, lighter hysteresis (1 up / 2 down). Use on 1m through 1H charts.
Swing (default) : ATR 14, lookback 200, smoothing 5. Balanced. Start here on 1H through 1D charts.
Long-Term Hold : ATR 20, lookback 300, smoothing 5. Slower, rarer events, heavier hysteresis (2 up / 3 down). Use on 1D and above.
Custom : full manual control of ATR Period, Lookback Window, and Smoothing.
Core settings:
Horizon : selects the tuning bundle above. Start with Swing.
ATR Period (Custom) : Wilder ATR period for the volatility input, in BARS. 14 is the standard. Shorter = more reactive; longer = smoother. Applies only when Horizon = Custom.
Lookback Window (Custom) : rolling lookback the ATR% is percentile-ranked against. Larger = smoother distribution, fewer extreme reads, slower compression releases. Smaller = sharper, more events.
Smoothing (EMA) (Custom) : EMA bars applied to the percentile-rank for the visual DISPLAY layer (plot, ribbon, panel readouts). The RAW rank still drives tier, phase, and events - smoothing only calms the visual. Set to 1 to disable smoothing.
Playbook Lens:
Neutral (default) : factual regime read, heatmap stays gray. Use this to learn the engine.
Breakout : range-expansion context. Loaded Compression and Compression Release read favorable; already-stretched Elevated or Extreme states shift toward caution.
Trend : directional-movement context. Rising Elevated and Rising Normal regimes read favorable; topping or cooling volatility shifts toward caution.
Mean Reversion : contained-range context. Quiet, Cooling, and Normal/Falling regimes read favorable; Release, Elevated, and Extreme regimes shift toward caution.
Risk Control : stretched-volatility context. Compression reads calm; Elevated and Extreme states warn that bar ranges are wide.
The Lens NEVER changes the engine - same tier, same phase, same Compression Release, same Extreme Touch, same alerts. Only the panel Playbook row text, the Heatmap Strip color, and the optional candle tint move.
Display:
Show Compression Releases (hero): diamond on the line + pane background pulse on release. On by default.
Show Extreme Touches : circle on the peak bar at rawRank >= 90. On by default.
Show Price Chart Markers : mirrors Compression Release diamonds and Extreme bar tints onto the price chart. OFF by default to keep the price chart clean.
Show Raw Rank Line : faint unsmoothed percentile rank line behind the smoothed display line. OFF by default. Toggle on to debug fast vol changes.
Show Volatility Glow : halo that widens at the loaded extremes (Compression and Extreme) and tightens in Normal. On by default.
Show Info Panel : 6-row state panel. On by default.
Panel Position : Top Right (default), Top Left, Bottom Right, Bottom Left, Middle Right.
Theme : Auto (detect chart background), Dark, or Light.
Show Playbook Heatmap Strip : thick band at y = -5 that recolors with the Lens. On by default.
Tint Price Candles by Playbook Fit : paints price-chart candles with the Release / Extreme palette per the active Lens. OFF by default; disabled automatically when Lens = Neutral.
Appearance / Palette (6 color pickers):
Compression, Quiet, Normal, Elevated, Extreme, Release - each on its own line with a state-explainer tooltip. The Display Rank line, Raw Rank, Tier Ribbon fill, Volatility Glow, Heatmap Strip, panel tier text, candle tints, and event markers all reference these inputs so users can adapt the palette (color-blind, light-mode, brand themes) without forking the script.
════════════════════════════════════════════
△ LIMITATIONS
Warm-up : the lookback window must fill before any tier is assigned. On Swing (200) that is 200 bars; on Long-Term Hold (300) that is 300. Until then, the panel shows "Warming up" and the state engine refuses to fake a Normal read.
Visual smoothing lag : the visible line is intentionally calmer than the raw engine. ATR is a backward-looking Wilder-smoothed measure, and the display line is lightly EMA-smoothed on top, so fast volatility expansions can look slightly delayed in the visible plot. The rawRank engine is the sharper layer underneath and is what actually drives the tier, phase, events, and alerts. The smoothed line is the readable copy; do not read a slight visual delay as the event engine being slow.
Percentile is relative, not absolute : a "Compression" read on a chronically quiet asset can still be wider than an "Elevated" read on a chronically loud asset. The indicator compares each asset against ITS OWN history, not across markets.
Regime shifts shrink the window : a structural vol regime change (e.g. a quiet 2-year period followed by a sustained higher-vol regime) takes about one lookback window to fully recalibrate. The first few weeks after a regime shift can read noisier than the steady-state.
Compression Release is non-directional : the diamond and the pane pulse tell you the spring released, not which way price went. Combine with directional context (trend, structure, or a separate momentum tool) for direction.
Extreme Touch is a state read, not a reversal call : rawRank pinning above 90 means vol is rare for this market; it does not mean price is about to reverse. Cooling tells you the unwind has begun, not where the next leg goes.
Playbook Lens is interpretation, not validation : the Heatmap Strip recolors regime context based on the active Lens. It is not a backtested edge - it is a quick visual answer to "does my workflow want this regime?"
════════════════════════════════════════════
🔔 ALERTS
Four alert conditions are built in so you can monitor without checking every bar manually:
Compression Release : a sustained compression (>= 10 bars) confirmed above mid-rank within 5 bars. The hero event.
Extreme Touch : rawRank peaked above P90. Fires on the bar after the actual peak (peak detection requires the next bar to confirm the turn-down).
Cooling : the first confirmed bar after an Extreme where rawRank falls below 75 within 10 bars.
Compression Entry : rawRank dropped below P25 (sustained tier transition into Compression).
All four alerts fire on bar close (gated on barstate.isconfirmed). Each alert message is a pure JSON payload with ticker, price, timeframe, and timestamp fields for webhook routing.
Four alerts by design - concentrated on the signature events. Tier and phase transitions stay visible in the info panel for users who want them on the chart, but they do not fire alerts. Keeping the alert stream lean is what makes "subscribe and let the regime come to you" a useful workflow instead of a notification flood.
════════════════════════════════════════════
⌁ NOTES
Based on the classical ATR percentile-rank construction, with asymmetric hysteresis and a velocity-gated compression-release definition layered on top.
Repaint: intrabar-only. Closed-bar alerts are confirmed; current-bar visuals may update until the bar closes. All alert conditions are gated on barstate.isconfirmed. Peak-confirmed events (Extreme Touch) print on the bar AFTER the actual peak, on a one-bar offset, so the marker aligns with the true peak bar.
References: J. Welles Wilder Jr., New Concepts in Technical Trading Systems (1978), Trend Research; percentile-rank concept widely used across volatility studies.
Open-source under MPL 2.0. Free to use, fork, study.
NovaLens Indicator
Index Futures Position Size Calculator V2A simple, free position size calculator for CME index futures traders.
Click Entry, click Stop Loss, pick your asset, get your contract size instantly. Built for fast NY session execution — no spreadsheets, no manual maths, no noise.
This is the updated version. The first release was a bare-bones calculator showing contract size only with a fixed SL buffer. This version is a full rebuild — every feature below came from real trading feedback, not theory.
═══════════════════════════════════
✦ SUPPORTED INSTRUMENTS
MNQ · MES · NQ · ES — all CME tick values hardcoded. No manual lookup, no mistakes.
═══════════════════════════════════
✦ WHAT IS NEW IN THIS VERSION
→ SL buffer is now a toggle — switch the auto ±1 handle offset on or off anytime from settings. When on, the SL label shows +1H so you always know what was calculated
→ Panel now shows four live values — asset, contract size, real USD risk after rounding, and full stop distance in points
→ Direction arrow — ▲ Buy or ▼ Sell auto-detected from your Entry and SL position
→ Panel size control — choose Small, Medium, Large or XL to fit any screen or preference
→ Lines now start exactly at your click point and extend right — no more lines appearing from far left
→ Price labels on both lines — see your exact Entry and adjusted SL price at a glance
→ Ghost line bug fixed — no more phantom line appearing at the bottom when switching timeframes
→ Dark PulseWire-native panel design — colour-coded values, clean two-column layout, easy to read at a glance during live sessions
═══════════════════════════════════
✦ FEATURES
→ One-click Entry and Stop Loss directly on the chart
→ Optional auto ±1 handle SL buffer — structural protection against wick hunts built in
→ Asset dropdown — MNQ, MES, NQ, ES with correct tick value loading automatically
→ Smart rounding — fractional contracts of 0.75 or higher round up, otherwise round down
→ Green Entry line and Red SL line from your exact click, both extending right
→ Live panel updates instantly when you move Entry or SL
═══════════════════════════════════
✦ HOW TO USE
Add to chart → click Entry → click Stop Loss → pick asset → set Account Size and Risk %. Read your size from the top-right panel. Three clicks and you are sized.
═══════════════════════════════════
✦ PROP FIRM CHALLENGE SIZING
Two clean methods to work within your max drawdown limit.
Method 1 — Loss budget split Divide your max loss by how many consecutive losses you can afford. Enter the result as Account Size with Risk at 100%. Example: $2,000 max loss ÷ 5 losses → Account Size $400 · Risk 100%
Method 2 — Direct percentage Enter your full max loss as Account Size and set your per-trade percentage. Example: $2,000 max loss, 20% per trade → Account Size $2,000 · Risk 20%
Both give the same result — use whichever feels natural.
═══════════════════════════════════
✦ A NOTE FROM THE AUTHOR
Built together with Claude AI through real iterative development — every single feature in this indicator exists because a real trade needed it.
This is 100% free and open source. No Discord, no course, no affiliate links, nothing to buy — ever.
You are completely free to copy this, modify it, rename it, improve it and republish it as your own. Seriously — go ahead. If you build something better on top of this, that is exactly the point. Clean tools should be free and open to everyone.
If it helps even one trader size their positions properly and protect their capital, it was worth sharing.
═══════════════════════════════════
✦ DISCLAIMER
Educational tool only. I do not take any responsibility when you use this indicator in your trading — always check the calculations before use. Futures trading carries substantial risk of loss. Not financial advice.
Built with ❤️ by REDz and Claude Indicator
Range Equilibrium Rotation Planner [AGPro Series]Range Equilibrium Rotation Planner
🧠 Core Idea
Is price rotating cleanly away from range equilibrium toward an edge, or is the midpoint still controlling the auction?
📌 Overview / What it does
Range Equilibrium Rotation Planner maps mature range structure and focuses on the midpoint equilibrium area instead of treating every range as a breakout setup.
The script displays the active range box, equilibrium band, edge rails, rotation room rail, failure rail, event labels, right-side tags, optional bar coloring, and a compact AG Pro dashboard with a 0-100 Rotation Score.
It does not predict range breaks. It helps organize range balance, midpoint control, directional rotation, edge room, failure risk, and next-action state.
🎯 Purpose & Design Philosophy
Many range tools focus on support, resistance, or breakout alerts.
This script was built for a different question: what happens inside the range before price reaches the edge?
It helps traders review whether price is still trapped around equilibrium or beginning a clean rotation from the midpoint toward the upper or lower edge.
⚡ Why This Script Is Different
Most range indicators draw a box and wait for a breakout.
This script does NOT center the workflow on range escape.
Instead, it evaluates range maturity, midpoint control, rotation quality, edge room, and failure back through equilibrium. The goal is rotation planning, not breakout prediction.
⚙️ Methodology
1. Range Maturity Detection
The script builds a rolling range using recent high and low structure, then checks whether the height and edge interactions are meaningful.
2. Equilibrium Mapping
The midpoint band is calculated around the center of the range and becomes the key control zone.
3. Rotation Evaluation
Price must move away from equilibrium with enough buffer before directional rotation is considered active.
4. Risk / Room Structure
The active edge becomes the room reference, while the opposite side of equilibrium becomes the failure area.
5. Visual Output
The chart receives a range box, equilibrium band, edge rails, room rail, failure rail, labels, right-side tags, optional bar coloring, and dashboard panel.
🗺️ How to Read the Chart
The range box marks the current high-to-low structure.
The equilibrium band shows the midpoint area where rotation control is evaluated.
The upper and lower rails mark the active range edges.
The room rail marks the edge being targeted by the active rotation.
The failure rail marks where rotation has moved back through the wrong side of equilibrium.
Labels highlight mature ranges, rotations from midpoint, equilibrium holds, edge reviews, and failed rotations.
Colors represent context:
• Teal → bullish rotation
• Pink → bearish rotation or failure
• Gold → equilibrium, room, or edge review
• Indigo → range structure or waiting context
The panel summarizes:
• Range
• Rotation Score
• Balance
• Room
• Action
🚦 Signals & States
• Range Ready → a mature range structure is available
• Bull Rotation → price rotated upward from equilibrium
• Bear Rotation → price rotated downward from equilibrium
• Midpoint Hold → price remains controlled by the equilibrium band
• Edge Review → price reached the active range edge
• Failed → rotation moved back through the failure rail
• READY → rotation quality and room are strong enough to monitor
• MONITOR → rotation is active but not fully ready
• WAIT RANGE → no mature range exists
• WAIT ROTATION → range exists but no clean rotation has started
🔔 Alerts Logic
Alerts can trigger when a mature range appears, when bullish or bearish rotation begins, when READY state appears, when midpoint hold appears, when an edge is reached, or when the rotation fails.
Alerts are attention markers only. They are not trade instructions.
🧩 Confluence Logic
The context becomes stronger when range maturity, balanced edge interaction, midpoint departure, edge room, and failure distance align.
The script avoids treating midpoint noise as a clean rotation without confirmation.
📊 When to Use
• Sideways markets with visible range structure
• Crypto, forex, indices, and liquid stocks
• 1H, 4H, and 1D market structure review
• Mean-reversion planning inside a range
• Range edge preparation without waiting for breakout-only logic
⚠️ When NOT to Use
• Strong one-directional trends with no range structure
• Thin symbols with unreliable highs and lows
• News-driven candles that distort range boundaries
• Very small ranges where spread or tick noise dominates
• Markets with unstable data or irregular sessions
🎛️ Key Inputs
• Range Lookback → controls the structure used to build the range
• Minimum / Maximum Range Height ATR → filters ranges that are too small or too wide
• Edge Touch Tolerance → controls how edge interactions are counted
• Equilibrium Band ATR → controls midpoint band width
• Rotation Break Buffer → controls how far price must move beyond equilibrium
• Minimum Ready Score → controls READY strictness
• Projection Bars → controls how far boxes, rails, and tags extend
• Visual settings → control labels, tags, panel location, theme, and font size
🖥️ Interface & Visual Design
The panel is designed to show the range state, rotation quality, balance, room, and action without overloading the chart.
The first row uses a merged AG Pro header. The chart layer keeps the range and equilibrium structure visible while leaving room for price action.
Labels are controlled with cooldown and maximum count settings to preserve a premium screenshot style.
🧪 Practical Usage Workflow
1. Read the panel.
2. Confirm a mature range exists.
3. Check whether price is still at equilibrium or rotating away.
4. Review room to the active edge.
5. Watch the failure rail if rotation loses control.
🔍 Interpretation Guidelines
A high score means range maturity, midpoint departure, and edge room are aligned.
A midpoint hold means equilibrium is still controlling the auction.
An edge review means the rotation has reached the active range edge and should be interpreted as context, not as an automatic exit.
A failed state means the active rotation moved back through its failure boundary.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an automated trading system.
It does not place orders.
It does not guarantee edge reach, reversal, breakout, or profitability.
⚠️ Limitations & Transparency
Range boundaries can shift as new highs or lows appear.
Different timeframes may show different range structures.
Large volatility events can temporarily distort range height and edge touch quality.
Low liquidity may create unreliable equilibrium or edge behavior.
The script is rule-based and should be interpreted within broader market context.
🧠 Market Context Notes
Equilibrium is often where the market decides whether price will rotate toward an edge or remain balanced.
The strongest rotation contexts usually appear when price leaves midpoint with room, while failure remains clearly defined.
This script is designed to make that inside-range decision point easier to read.
🧾 Use Case Examples
When price holds near midpoint and then closes above the equilibrium band, the script can begin tracking bullish rotation toward the upper range edge.
When price rotates downward from equilibrium and reaches the lower edge, the context shifts into edge review rather than fresh entry signaling.
When price moves back through the failure rail, the active rotation context fails.
🧱 System Philosophy
AGPro Series tools are built as decision-support systems.
They aim to convert market structure into readable context: what is active, what improves the plan, what invalidates it, and what should be reviewed next.
🔐 Non-Promise Statement
No script can provide certainty.
No signal guarantees outcome.
This tool provides structured context only.
📉 Risk Disclosure
Trading involves risk.
Markets can move quickly and unexpectedly.
Users are responsible for their own analysis, risk management, and decisions.
This script does not provide financial advice.
📚 Educational Note
Use this tool to study how range equilibrium, midpoint control, rotation quality, and edge room interact across different symbols and timeframes.
Indicator
Trend Exhaustion Snapback Planner [AGPro Series]Trend Exhaustion Snapback Planner
🧠 Core Idea
Is the current trend stretch becoming snapback-ready, or is momentum still supported enough to avoid calling exhaustion too early?
📌 Overview / What it does
Trend Exhaustion Snapback Planner is a rule-based trend exhaustion and mean-reversion planning tool. It measures how far price has stretched away from its trend mean, then evaluates whether that stretch is supported by pressure, efficiency loss, wick behavior, and room back toward value.
The script produces an exhaustion pocket, snapback rail, failure rail, room reference, event labels, right-side tags, optional bar coloring, and a compact AG Pro dashboard with a 0-100 Snapback Score.
It does not predict reversals. It helps organize trend stretch, exhaustion quality, snapback reclaim behavior, failure risk, and next-action state.
🎯 Purpose & Design Philosophy
Strong trends can stay stretched for longer than expected. At the same time, many reversals begin only after a trend becomes inefficient and price starts moving back toward value.
This script was built to help traders review that transition without relying on a simple overbought or oversold reading.
It supports a patient workflow: identify stretch, wait for reclaim behavior, evaluate room, then interpret the active state within broader market context.
⚡ Why This Script Is Different
Most exhaustion tools focus on RSI extremes, distance from a moving average, or isolated reversal candles.
This script does NOT treat every stretched move as a reversal.
Instead, it maps a live exhaustion pocket, scores stretch quality, tracks snapback reclaim behavior, defines where the idea fails, and shows whether there is room back toward the trend mean.
⚙️ Methodology
1. Trend Stretch Detection
The script measures price distance from a trend mean using ATR normalization.
2. Pressure Evaluation
RSI pressure, wick behavior, and trend-efficiency loss are reviewed to decide whether the extension is weakening.
3. Snapback Rail Mapping
Once a valid exhaustion pocket appears, the snapback rail becomes the first reclaim threshold.
4. Risk / Room Structure
The failure rail marks continuation risk, while the room rail shows the value or structure reference that price may test after reclaim.
5. Visual Output
The chart receives the exhaustion pocket, trend mean, snapback rail, failure rail, room rail, event labels, right-side tags, optional bar coloring, and dashboard panel.
🗺️ How to Read the Chart
The exhaustion pocket marks the stretch area created after price moves far away from its trend mean.
The snapback rail shows the reclaim level that improves the snapback context.
The failure rail marks where continuation risk invalidates the active snapback idea.
The room rail shows the next value or structure reference after the snapback begins.
Labels highlight stretch pockets, snapback reclaim, pocket pressure, room tests, and failed snapbacks.
Colors represent context:
• Teal → bullish snapback context
• Pink → bearish snapback context or failure
• Gold → room, waiting, or neutral review
• Indigo → pocket pressure or monitoring context
The panel summarizes:
• Pocket
• Snapback Score
• Stretch
• Room
• Action
🚦 Signals & States
• Bull Snapback Pocket → downside trend stretch with bullish snapback context
• Bear Snapback Pocket → upside trend stretch with bearish snapback context
• Snapback Reclaim → price reclaimed the active snapback rail
• Pocket Pressure → price is testing the exhaustion pocket without clean reclaim
• Room Test → price reached the active room reference
• Failed → price crossed the failure rail
• READY → reclaim and score quality are strong enough to monitor
• MONITOR → snapback context is active but not fully ready
• WAIT RECLAIM → pocket exists but reclaim has not confirmed
• EXPIRED → the pocket is too old to remain active
🔔 Alerts Logic
Alerts can trigger when a bullish or bearish snapback pocket appears, when price reclaims the snapback rail, when the READY state appears, when pocket pressure appears, when the room rail is reached, or when the context fails.
Alerts are attention markers only. They are not trade instructions.
🧩 Confluence Logic
The context becomes stronger when ATR stretch, RSI pressure, wick behavior, efficiency loss, snapback reclaim, and room back toward value align.
No single condition is treated as enough by itself.
📊 When to Use
• Mature directional moves
• Strong extensions away from trend mean
• Markets with visible impulse and reaction structure
• 1H, 4H, and 1D review where exhaustion context matters
• Crypto, indices, forex, and liquid stocks
⚠️ When NOT to Use
• Extremely illiquid symbols
• Very low-volume periods
• News shock candles with abnormal gaps
• Very tight ranges with no meaningful trend stretch
• Markets where spreads or wicks dominate the structure
🎛️ Key Inputs
• ATR Length → normalizes trend stretch and rail distances
• Trend Mean Length → controls the main value reference
• Minimum Stretch ATR → controls how stretched price must be before a pocket appears
• RSI Pressure → controls pressure thresholds for extended conditions
• Efficiency Length → controls how trend efficiency loss is measured
• Minimum Ready Score → controls how strict READY classification is
• Projection Bars → controls how far rails and zones extend
• Visual settings → control labels, tags, panel location, theme, and font size
🖥️ Interface & Visual Design
The panel is designed as a compact decision dashboard, not a large data table.
The first row uses a merged AG Pro header. The remaining rows show the pocket state, score, stretch context, room, and action.
The visual hierarchy is built so traders can read the active plan quickly without losing chart structure.
🧪 Practical Usage Workflow
1. Read the panel.
2. Check whether an exhaustion pocket is active.
3. Watch the snapback rail for reclaim behavior.
4. Review failure risk and room back toward value.
5. Interpret labels as context markers, not trade commands.
🔍 Interpretation Guidelines
A high score means the active stretch has multiple snapback conditions aligned.
A snapback reclaim improves the context, but it does not guarantee continuation toward the room rail.
A failed state means price crossed the continuation-risk boundary for that active pocket.
Use the script to organize the question, not to outsource the answer.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not financial advice.
It is not an automated trading system.
It does not place orders.
It does not guarantee reversal timing, target reach, or profitability.
⚠️ Limitations & Transparency
Trend exhaustion can remain extended for long periods.
Different timeframes may show different exhaustion and snapback contexts.
Volatility spikes can distort ATR-normalized distance.
Low liquidity can create false stretch pockets or unreliable wick behavior.
The script is rule-based and should be interpreted within broader market context.
🧠 Market Context Notes
Trend exhaustion is not the same as trend reversal.
The most useful snapback contexts often appear when price stretches away from value, momentum efficiency weakens, and reclaim behavior begins before the failure rail breaks.
The strongest readings usually come from alignment between structure, volatility, and reaction quality.
🧾 Use Case Examples
When price stretches far above the trend mean, RSI pressure rises, and the candle begins reclaiming back through the snapback rail, the bearish snapback context may become more meaningful.
When price stretches below the trend mean but cannot reclaim the snapback rail, the script may remain in WAIT RECLAIM or PRESSURE instead of READY.
When price reaches the room rail after reclaim, the context shifts into room review rather than fresh entry signaling.
🧱 System Philosophy
AGPro Series tools are built as decision-support systems.
They aim to convert market structure into readable context: what is active, what improves the plan, what invalidates it, and what should be reviewed next.
🔐 Non-Promise Statement
No script can provide certainty.
No signal guarantees outcome.
This tool provides structured context only.
📉 Risk Disclosure
Trading involves risk.
Markets can move quickly and unexpectedly.
Users are responsible for their own analysis, risk management, and decisions.
This script does not provide financial advice.
📚 Educational Note
Use this tool to study how trend stretch, momentum pressure, efficiency loss, and snapback behavior interact across different markets and timeframes.
Indicator
Volume Dry-Up Reversal Planner [AGPro Series]Volume Dry-Up Reversal Planner
🧠 Core Idea
Is the market losing participation before a reversal attempt?
📌 Overview / What it does
Volume Dry-Up Reversal Planner detects low-participation pockets where relative volume contracts and candle range compresses.
The script maps a dry-up pocket, tracks whether price attempts to reverse out of that pocket, and displays reversal rails, failure shelves, follow-through references, event labels, and a compact AG Pro dashboard.
It does not predict reversals. It helps organize participation, compression, reaction quality, failure risk, and current action state around a potential dry-up reversal context.
🎯 Purpose & Design Philosophy
Many reversal tools focus on dramatic exhaustion candles or high-volume climaxes.
This script was built for a quieter but important condition: participation drying up before the next reaction.
It helps traders evaluate whether the market is simply inactive, compressing before movement, or beginning a structured reversal attempt from a low-participation pocket.
⚡ Why This Script Is Different
Most volume indicators highlight high-volume events.
This script does NOT chase volume climax or generic reversal signals.
Instead, it focuses on volume dry-up, range compression, reversal rails, failure shelves, follow-through context, and a 0-100 readiness score.
⚙️ Methodology
1. Participation Detection
The script compares current volume against recent average volume to identify low-participation candles.
2. Compression Mapping
Current candle range is compared with recent average range. A dry-up pocket requires both lower participation and controlled range compression.
3. Reversal Evaluation
After a dry-up pocket appears, the script watches whether price breaks beyond the pocket with enough quality to form a reversal attempt.
4. Visual Output
The chart receives a dry-up pocket, reversal rail, failure shelf, follow-through rail, right-side tags, event labels, optional bar coloring, and a dashboard panel.
🗺️ How to Read the Chart
The dry-up pocket marks the area where participation and range compressed.
The reversal rail shows the level price must clear to begin a reversal attempt.
The failure shelf marks where the active reversal context fails.
The follow-through rail marks the first reaction reference after a reversal attempt.
Labels highlight dry-up pockets, bullish reversal attempts, bearish reversal attempts, follow-through, and invalidation.
Colors represent context:
• Teal → bullish reversal attempt
• Pink → bearish reversal attempt or invalidation
• Gold → follow-through or waiting context
• Indigo → dry-up pocket / monitoring context
The panel summarizes:
• Dry-Up state
• Reversal Score
• Participation
• Failure Risk
• Action
🚦 Signals & States
• Dry-Up Pocket → relative volume and range both contracted
• Bull Reversal → price broke above the dry-up pocket
• Bear Reversal → price broke below the dry-up pocket
• Follow-Through → price reached the first reaction rail
• Invalidated → price crossed the failure shelf after a reversal attempt
• READY → reversal context has enough score quality to monitor
• MONITOR → reversal attempt is active but not fully ready
• WAIT → no strong active context exists
• EXPIRED → the dry-up pocket is too old to remain active
🔔 Alerts Logic
Alerts can trigger when a dry-up pocket appears, when a bullish or bearish reversal attempt begins, when the context reaches READY state, when follow-through appears, or when invalidation occurs.
Alerts are attention markers only. They are not trade instructions.
🧩 Confluence Logic
The context becomes stronger when relative volume contraction, range compression, close response, rejection quality, and volatility fit align.
For example, a low-volume compression pocket followed by a strong close outside the pocket can create a more structured reversal context than a random low-volume candle.
📊 When to Use
• Potential reversal areas after participation fades
• Pullback zones where volume dries up
• Ranging markets before directional reaction
• Trend pauses where continuation or reversal depends on participation
• Liquid crypto, indices, forex, and equities with readable volume behavior
⚠️ When NOT to Use
• Very low-liquidity symbols
• Markets with unreliable volume data
• News spikes and unstable spread conditions
• Extremely noisy candles without structure
• Situations where low volume simply means no meaningful market participation
🎛️ Key Inputs
• Relative Volume Length → controls the volume baseline
• Dry-Up Volume Threshold → controls how strict low-participation detection is
• Range Compression Length → controls the range baseline
• Maximum Range Ratio → controls how compressed the candle must be
• Dry-Up Pocket Window → controls how the pocket is mapped
• Reversal Buffer ATR → controls how far price must clear the pocket
• Failure Shelf ATR → controls where the reversal context fails
• Follow-Through ATR → controls the first reaction reference
• Visual settings → control pockets, rails, labels, tags, panel, and bar colors
🖥️ Interface & Visual Design
The interface is designed to make participation shifts visible without turning the chart into a noisy signal board.
The dry-up pocket defines context, the reversal rail defines the first reaction threshold, the failure shelf defines risk, and the panel summarizes the current state.
The goal is a premium, readable visual map for traders who care about participation and reaction quality.
🧪 Practical Usage Workflow
1. Check whether a dry-up pocket is active
2. Read the panel score and action state
3. Watch the reversal rail
4. Compare follow-through with failure risk
5. Confirm the context with broader market structure and timeframe alignment
🔍 Interpretation Guidelines
A dry-up pocket means participation and range compressed. It does not mean a reversal must happen.
A reversal attempt means price broke out of the pocket with enough reaction to monitor.
A READY state means the rule-based score has enough quality for attention.
Failure risk helps keep the reversal context grounded instead of treating every low-volume area as important.
🚫 What This Script Is NOT
This script is not a prediction engine.
It is not a guaranteed reversal system.
It is not a high-volume climax detector.
It is not an automated trading tool.
It does not provide financial advice.
It does not guarantee reversal, continuation, profit, or a specific target.
⚠️ Limitations & Transparency
Volume behavior differs across markets, exchanges, sessions, and timeframes.
Some dry-up pockets may lead to no meaningful reaction.
Some reversals may begin without a clean dry-up pattern.
The score is a rule-based context score, not a certainty model.
🧠 Market Context Notes
Volume dry-up can represent hesitation, absorption, exhaustion, or simple inactivity.
The important question is not whether volume is low by itself, but whether price reacts cleanly after participation contracts.
Use the pocket as context, not confirmation by itself.
🧾 Use Case Examples
When price pulls back with shrinking volume and compressed candles, the script can map a dry-up pocket.
If price later breaks above that pocket, the script marks a bullish reversal attempt and tracks follow-through.
If price breaks below the failure shelf after a reversal attempt, the script marks invalidation.
🧱 System Philosophy
This script follows the AGPro Series approach: turn a specific market condition into a structured decision-support map.
The focus is not prediction. The focus is participation, compression, reaction quality, failure awareness, and visual clarity.
🔐 Non-Promise Statement
No script can remove uncertainty from markets.
This tool does not promise accuracy, profitability, or future price movement.
Its purpose is to organize volume dry-up context so the user can interpret the chart more clearly.
📉 Risk Disclosure
Trading involves risk.
Market conditions can change quickly, and any analytical output can fail.
Users are responsible for their own decisions, risk management, and trade execution.
This script is for educational and analytical purposes only and does not provide financial advice.
📚 Educational Note
Low volume is not automatically bullish or bearish.
The best reads usually come when volume dry-up, range compression, reaction quality, and market structure all support the same context.
Indicator
