Indicator
Decision Point Planner [AGPro Series]Decision Point Planner
🧠 Core Idea
Is price sitting at a decision point that deserves review, patience, or rejection?
📌 Overview / What it does
Decision Point Planner is a chart-first risk planning tool built to evaluate whether the current price area is meaningful enough to deserve attention.
The script maps one active decision point from structure shelf, balance edge, or trend backbone context, then scores the area using location quality, reaction candle behavior, volume support, trend context, available room, and invalidation distance. The output is a 0-100 Decision Score, a clear next-action state, a decision zone, an invalidation shelf, a target-room corridor, compact labels, alerts, and a premium AGPro panel.
It does not predict price direction, automate execution, or print direct buy/sell signals.
🎯 Purpose & Design Philosophy
This script was built for traders who want to know whether the chart is actually at a meaningful decision area or simply moving through noise.
Many tools show levels, zones, or signals in isolation. Decision Point Planner focuses on a narrower planning question: if price is near a decision reference, is the reaction strong enough, is risk still balanced, and is there enough room before the next obstacle?
The design supports a patient planning mindset: identify the point, read the reaction, check room and invalidation, then decide what deserves attention.
⚡ Why This Script Is Different
Most tools focus on plotting many support/resistance levels or marking every reaction.
This script does NOT create a generic S/R map, order-block scanner, FVG map, or prediction engine.
Instead, it selects one active decision reference and turns it into a planning workflow: Decision Score, Zone Type, Reaction State, Room/Risk, and Next Action.
⚙️ Methodology
1. Context Detection
The script detects the active planning side automatically using trend context and range location, or the user can force Long Context or Short Context.
2. Reference Mapping
It compares three decision references: the latest structure shelf, the active balance edge, and the trend backbone. The closest relevant reference becomes the active decision point.
3. Reaction Evaluation
It evaluates whether price is touching or approaching the zone, whether the candle shows a valid reaction, whether volume supports the reaction, whether trend context agrees, and whether room and invalidation remain balanced.
4. Visual Output
It displays a decision zone, invalidation shelf, target-room corridor, compact chart labels, alerts, and a clean AGPro panel.
🗺️ How to Read the Chart
Decision Zone = the current area where price is being evaluated as a decision point.
Invalidation Shelf = the reference beyond the zone that marks rejection in this rule set.
Target-Room Corridor = the available forward room toward the nearest obstacle or a minimum room guide.
Labels = compact attention markers showing ACTION, WAIT, PATIENCE, REJECTED, ROOM, or D POINT context.
Colors = teal and pink show active directional context, amber shows caution, indigo shows wait/reaction context, and blue is reserved for the AGPro panel header.
Panel = summarizes Decision Score, Zone Type, Reaction State, Room Risk, and Action.
🚦 Signals & States
• ACTION REVIEW → the decision point has enough score, reaction, room, and risk quality to deserve closer review.
• WAIT REACTION → price is near the decision point, but the reaction is still incomplete.
• PATIENCE → the area is active but quality, room, or risk is not clean enough yet.
• REJECTED → price crossed the invalidation shelf for the active decision point.
• STAND BY → price is not close enough to the active decision reference.
🔔 Alerts Logic
• Decision Point Action Review → triggers when the state enters ACTION REVIEW.
• Decision Point Wait Reaction → triggers when price is near the point but reaction is incomplete.
• Decision Point Patience → triggers when the active point requires patience or broader confirmation.
• Decision Point Room Limited → triggers when the point is active but forward room is limited.
• Decision Point Rejected → triggers when price crosses the active invalidation shelf.
Alerts are attention markers. They are not trade instructions.
🧩 Confluence Logic
Decision quality improves when location, reaction candle behavior, volume support, trend context, target room, and invalidation distance align.
The strongest read appears when price is near the decision zone, the reaction candle is efficient, volume is supportive, trend context agrees, room is open, and risk distance is balanced.
📊 When to Use
• Around pullbacks where price is near a meaningful planning reference.
• During breakout or continuation preparation when the next reaction matters.
• Near range edges or balance transitions where patience is required.
• When comparing whether a setup deserves review or should remain on watch.
• On liquid markets where ATR, volume, and recent structure are meaningful.
⚠️ When NOT to Use
• Extremely low-liquidity markets with unreliable volume and candles.
• Highly noisy micro-timeframes where decision references change too frequently.
• News-driven volatility spikes where ATR and candle ranges expand abnormally.
• Charts where the user expects automatic buy/sell signals.
• As a standalone reason to enter or exit a trade.
🎛️ Key Inputs
• Planning Side → selects Auto, Long Context, or Short Context.
• Decision Range Lookback → defines the planning range and target-room obstacle.
• Structure Shelf Pivot Length → controls how strict the structure shelf reference is.
• Decision Reach ATR → controls how close price must be to the active point before review.
• Decision Zone Half-Width ATR → controls the vertical size of the decision zone.
• Target Room and Invalidation Inputs → define room quality and balanced risk distance.
• Visual Settings → control zones, shelves, corridor, labels, panel location, panel theme, and font sizes.
🖥️ Interface & Visual Design
The interface is intentionally chart-first.
The script uses one active decision zone, one invalidation shelf, and one target-room corridor instead of filling the chart with many competing zones. Labels are compact, offset away from candles, and controlled with cooldown and maximum-visible settings.
The panel follows the AGPro publication layout with a single merged blue title row, adjustable location, adjustable theme, and adjustable font size.
🧪 Practical Usage Workflow
1. Read the panel state and Decision Score.
2. Check the active decision zone and zone type.
3. Evaluate the reaction label and candle behavior.
4. Compare target-room corridor and invalidation shelf.
5. Treat alerts as review markers and confirm the broader market context.
🔍 Interpretation Guidelines
A higher Decision Score means the active decision point has stronger alignment inside the script's rule set. It does not mean price must move in the planned direction.
ACTION REVIEW means the area deserves attention, not automatic execution.
WAIT REACTION means the location may be important but the reaction is not complete.
REJECTED means the active invalidation shelf was crossed in this rule set.
🚫 What This Script Is NOT
• Not a prediction engine.
• Not financial advice.
• Not auto trading.
• Not guaranteed signals.
• Not a buy/sell signal service.
• Not a generic support/resistance zone map.
• Not an order-block or FVG scanner.
⚠️ Limitations & Transparency
Decision quality depends on the selected lookback, pivot length, ATR behavior, volume reliability, and timeframe.
Different markets can produce different reference behavior. High volatility can widen invalidation distance. Low volatility can compress target room. Small timeframes may produce more frequent state changes.
The script is rule-based and should be interpreted as an analytical planning layer inside broader market context.
🧠 Market Context Notes
A decision point is useful only when it connects location, reaction, risk, and room.
The same visual area can be weak if reaction is poor, volume is absent, target room is blocked, or invalidation is too tight or too wide.
This script organizes those checks into one readable decision layer.
🧾 Use Case Examples
When price pulls back toward the decision zone and the panel moves from WAIT REACTION to ACTION REVIEW, the area may deserve closer review.
When price touches the zone but the panel shows Room Limited, the user can recognize that the nearby path is obstructed.
When price crosses the invalidation shelf, the script marks the active decision point as rejected inside its rule set.
🧱 System Philosophy
Decision Point Planner follows the AGPro decision-engine approach:
Context first.
Risk before reaction.
Room before confidence.
Attention markers instead of promises.
🔐 Non-Promise Statement
No script can guarantee direction, continuation, reversal, or outcome.
This tool provides structured chart context only.
📉 Risk Disclosure
Trading involves risk.
Users are responsible for their own analysis, risk controls, position sizing, and trading decisions.
This script does not provide financial advice, investment advice, or guaranteed trading outcomes.
📚 Educational Note
Use the script to study how decision quality changes as price moves closer to or away from active planning references.
The most useful reading comes from comparing the panel state with visible price reaction, room, and invalidation context.
Indicator
Execution Window Planner [AGPro Series]Execution Window Planner
🧠 Core Idea
Where is the cleanest active price window for evaluating execution context?
📌 Overview / What it does
Execution Window Planner is a chart-first execution-readiness tool built to answer one practical question: is price currently sitting inside a clean review window, or is the context too early, too late, too stretched, or already invalidated?
The script maps an active execution window box, a risk edge, a target edge, compact state labels, and a premium AGPro panel. It converts window width, structure alignment, volatility fit, trend support, candle confirmation, and room-to-risk context into a transparent 0-100 Quality Score.
It does not predict price movement, automate orders, or issue buy/sell commands. The output is designed as an analytical planning layer for traders who want cleaner context before making their own execution decisions.
🎯 Purpose & Design Philosophy
This script was built for traders who already have a directional thesis but need a disciplined way to judge whether the current price area is actually usable for execution review.
Many tools show trend, signals, support/resistance, or zones. The missing piece is often the active decision window: the price area where risk is still definable, target room still exists, volatility is not distorted, and confirmation is not too weak.
The design philosophy is simple: execution quality should be evaluated through a defined window, not through excitement around a single candle.
⚡ Why This Script Is Different
Most tools focus on printing a signal, marking a generic support/resistance area, or showing a large multi-feature trading dashboard.
This script does NOT act as a full trading suite, signal service, position sizing tool, ICT/FVG map, order block map, or generic zone scanner.
Instead, it keeps one narrow purpose: identify and score the current execution window using risk edge, target edge, structure, volatility, trend support, and candle confirmation. The result is a focused decision layer rather than another broad indicator.
⚙️ Methodology
1. Context Detection
The script detects the active planning side automatically from trend structure, or lets the user force a long-bias or short-bias view.
2. Reference Mapping
It builds a risk edge from recent structure and a target edge from broader structure or ATR-adjusted room.
3. Window Construction
It creates an active execution window around the current trend reference, then limits that window between the risk edge and target edge.
4. Reaction Evaluation
It scores window width, structure alignment, volatility fit, trend support, and candle confirmation into a 0-100 Quality Score.
5. Visual Output
The chart displays the execution window box, risk/target edges, state labels, alerts, and a premium AGPro panel with the key decision fields.
🗺️ How to Read the Chart
Execution Window = the current price area where the script is evaluating execution context.
Risk Edge = the structure-based invalidation edge for the active window.
Target Edge = the nearest meaningful target-side reference or ATR-adjusted room marker.
Labels = the current window state, score tier, risk distance, and room-to-risk context.
Colors = teal for stronger bullish execution windows, pink for bearish or invalidation contexts, amber for forming/waiting states, and indigo for target-edge or transition states.
Panel = the fastest summary of window state, quality score, risk edge, target edge, and next action.
🚦 Signals & States
• ACTIVE → the execution window meets the quality threshold and confirmation filter.
• FORMING → the window is improving but still needs cleaner confirmation.
• WAIT → the context exists, but structure, volatility, room, or confirmation is not strong enough yet.
• BLOCKED → there is no clean execution window in the current context.
• TARGET EDGE → price has reached the mapped target-side reference and reaction quality should be evaluated.
• INVALIDATED → price closed beyond the active risk edge.
🔔 Alerts Logic
ACTIVE Window alerts trigger when the state upgrades into ACTIVE.
Downgrade alerts trigger when the active window weakens from a stronger previous state.
Risk Edge alerts trigger when price closes beyond the current risk edge.
Target Edge alerts trigger when price reaches the current target edge.
Alerts are attention markers only. They are not trading instructions.
🧩 Confluence Logic
The strongest execution-window context appears when several conditions align:
• Price remains inside the mapped execution window
• The risk edge is still structurally valid
• The target edge leaves enough room relative to risk
• Trend support agrees with the active side
• Candle structure confirms the same direction
• Volatility is close to its recent baseline
When these elements align, the Quality Score improves and the panel state becomes easier to interpret.
📊 When to Use
• When you already have a directional thesis and want to evaluate execution context
• During trend continuation setups where risk and target references remain clear
• Around pullback or reset areas where timing and risk quality matter
• Before reacting to a potential continuation candle
• When you want a cleaner planning layer instead of another simple signal indicator
⚠️ When NOT to Use
• During very low-liquidity conditions where candles print irregularly
• During high-noise chop where risk and target edges change too quickly
• During extreme volatility spikes where ATR context becomes distorted
• On symbols with poor price continuity or unreliable session behavior
• As a standalone reason to enter or exit a trade
🎛️ Key Inputs
• Setup Direction → Auto detects the active planning side, or the user can force Long Bias / Short Bias.
• Sensitivity → controls how selective the model is.
• Structure Lookback → controls how risk edge, target edge, and structure context are mapped.
• Minimum ACTIVE Score → defines the score threshold required for ACTIVE state.
• Confirmation Mode → controls how much trend and candle confirmation must align.
• Label Cooldown Bars → controls historical label density.
• Max Visible Labels → limits older state labels to keep the chart readable.
• Label Detail → Compact is the default clean publication view; Balanced and Full can show more risk/room context.
• Label Offset Strength / Lane Strength → smart placement controls that keep labels near price without burying them inside candles or pushing them too far away on higher timeframes.
• Panel Location / Theme / Font Size → controls the AGPro panel presentation.
• Label Font Size → controls all on-chart labels.
🖥️ Interface & Visual Design
The panel is designed as a compact decision dashboard, not a large command center. The first row uses the standard AGPro merged blue header row, and the remaining rows focus only on the information needed to evaluate the current execution window.
The chart visuals stay restrained: one active execution window, one risk edge, one target edge, a current quality tag, and moderate historical state labels. The goal is a premium, readable chart that does not feel empty but also avoids clutter.
🧪 Practical Usage Workflow
1. Read the panel state first.
2. Check whether price is inside or near the execution window.
3. Compare the risk edge and target edge.
4. Review the Quality Score and confirmation state.
5. Interpret labels as context markers, not as trade commands.
6. Confirm the broader market context with your own process.
🔍 Interpretation Guidelines
ACTIVE does not mean guaranteed continuation. It means the current window has passed the script's rule-based quality model.
FORMING means the setup may be developing, but the script does not yet see enough confirmation.
WAIT means the context may exist, but the window quality is not clean enough.
BLOCKED means the current chart does not offer a useful execution window under the selected settings.
TARGET EDGE means the chart has reached the mapped target-side reference, so reaction quality becomes more important than chasing the move.
INVALIDATED means the risk edge has been broken and the active window should be reset.
🚫 What This Script Is NOT
• Not a prediction engine
• Not financial advice
• Not an auto-trading system
• Not a guaranteed signal tool
• Not a full trading suite
• Not an ICT/FVG or order block map
• Not a generic support/resistance zone scanner
⚠️ Limitations & Transparency
Execution-window quality is rule-based and depends on the selected inputs, timeframe, symbol behavior, and available chart data.
Different timeframes can produce different risk and target edges because market structure changes with resolution.
Fast volatility expansion can make the current edge distances less stable.
Low-volume markets may produce weaker confirmation quality.
The script should be interpreted inside broader market context, not in isolation.
🧠 Market Context Notes
Execution quality is usually strongest when structure, volatility, and trend behavior are aligned.
If volatility expands too quickly, the window can become stretched even if direction looks strong.
If the target edge is too close, the setup may have limited room even when the trend looks clean.
If the risk edge is too far away, the setup may require too much tolerance relative to the available room.
🧾 Use Case Examples
When price pulls back toward the active trend reference, remains inside the execution window, and the risk edge is still structurally protected, the Quality Score may improve.
When price reaches the target edge after an ACTIVE window, the script can shift into TARGET EDGE state so the user can evaluate reaction behavior instead of treating the move as fresh.
When price closes beyond the risk edge, the window becomes INVALIDATED and the panel shifts to a reset-oriented state.
🧱 System Philosophy
Execution Window Planner follows the AGPro Series approach: build scripts that help traders make a decision, not just see another signal.
The script is intentionally narrow. It focuses on one practical question and keeps the chart output centered around that question.
🔐 Non-Promise Statement
No script can provide certainty.
No score guarantees future movement.
No alert should be treated as an instruction to trade.
📉 Risk Disclosure
Trading involves risk.
Users are responsible for their own analysis, execution choices, risk management, and trading outcomes.
This script is for educational and analytical use only and does not provide financial advice.
📚 Educational Note
The best use of this script is to study how execution context changes as price moves between risk edge, execution window, and target edge.
Use it as a structured planning aid, not as a replacement for your own market analysis.
Indicator
TrueMove: Council of 7 Schools [TechnicalZen]A Decision Support System for Risk Management.
Imagine seven analysts — each a specialist in a different discipline — studying the same price chart simultaneously. One reads volume flow. Another scores multi-factor confluence. A third measures Wyckoff effort dynamics. A fourth compares wave speed and amplitude. A fifth tracks volume-weighted momentum. A sixth applies adaptive Kalman filtering. A seventh learns patterns from the instrument's own history using machine learning. Each arrives at their own independent conclusion. Then they vote.
This is what this indicator does. Seven academically grounded analytical Schools, each examining price action through a fundamentally different lens, casting independent votes on market direction. The result is not a prediction — it is a decision support system designed to help traders manage risk with confidence.
The core question it answers: "Is this move real, or is it a trap?"
When the council reaches consensus, you trade with conviction. When it doesn't, you wait. The strength of this system is not in any single School — it is in the convergence of independent perspectives. A move confirmed by volume flow, momentum, wave dynamics, and machine learning simultaneously carries fundamentally different weight than a move flagged by one method alone.
This is risk management through structured consensus. Not a black box. Not a single signal line. A council of seven independent minds, each with a transparent methodology, each with a tracked hit rate, each accountable for its calls.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The System
The indicator operates on three layers:
Signal Layer — Seven independent Schools analyze price action using different methodologies. Each votes Bull or Bear when its conditions are met.
Council Layer — Votes are aggregated. In "2+ Agree" mode, a signal fires only when two or more Schools vote in the same direction within a 3-bar window. In "All Signals" mode, any School's vote fires a signal.
Visual Layer — POC lines (anchored VWAP), EVWAP (exponentially weighted VWAP), risk/reward boxes, and direction labels present the council's verdict on the price chart.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The Council
The council aggregates school votes using a configurable consensus mechanism:
"2+ Agree" Mode — Requires two or more enabled Schools to vote in the same direction within a 3-bar window. This is the conservative mode. Fewer signals, higher conviction. If only one School is enabled, it automatically drops to requiring just that one vote.
"All Signals" Mode — Any enabled School's vote fires a signal. This is the aggressive mode. More signals, lower filtering. Useful for seeing what each School detects independently.
Conflict Resolution — If bull and bear votes arrive on the same bar, the direction with more votes wins. If tied, bull wins (consistent tie-breaking).
Cooldown — Separate bull and bear cooldowns prevent signal spam in the same direction while allowing quick reversals when the market genuinely flips.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The 7 Schools
Each School uses a fundamentally different analytical approach. They are designed to be independent — a signal from one School does not depend on or duplicate another.
School 1: OBV Flow
What it sees: Volume flow divergence and acceleration
Detects when On-Balance Volume diverges from price (hidden buying or selling pressure) and when volume flow is accelerating in a direction supported by market structure.
School 2: Confluence
What it sees: Multi-factor agreement across independent indicators
Triggers when RSI exits oversold (bull) or crosses below the momentum midline (bear) in a trending market. Scores seven independent factors and requires four or more to agree.
School 3: Wyckoff
What it sees: Effort vs Result on pullbacks, plus trap events
Measures whether pullback volume is declining relative to pre-pullback volume (Wyckoff effort), whether the bounce bar shows commitment (result), and detects Spring and Upthrust events — false breakdowns and breakouts that trap weak hands.
School 4: Amplitude Strength
What it sees: Wave dynamics — speed, time, and volume at swing points
Compares consecutive swing waves: is the trend wave faster than the pullback? Is the pullback shorter in time? Is volume declining at successive swing lows (or highs)? Is momentum oversold (or overbought) at the swing point? Scores seven wave-quality factors.
School 5: VWMA Delta
What it sees: Volume-weighted momentum crossing fair value
Computes the difference between short-term and long-term Volume Weighted Moving Averages, smooths it with RMA, and fires when this delta crosses zero. Volume is built into the measurement itself — not added as a secondary filter.
School 6: Kalman Filter (LQE)
What it sees: Adaptive filtered trend crossover
Applies two Kalman filters (Linear Quadratic Estimator) to price at different speeds. The short filter crossing above or below the long filter signals a trend shift. The Kalman filter adapts its responsiveness automatically based on estimation uncertainty.
School 7: Naive Bayes (Adaptive)
What it sees: Learned patterns in raw price action DNA
A machine learning classifier that observes six raw features no other School uses: body trend, wick dominance, price percentile, volatility regime, momentum acceleration, and gap behavior. It builds Gaussian probability profiles from resolved outcomes and votes when its confidence exceeds 65% in either direction. This School learns and adapts to the specific instrument and timeframe over time.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
School Rules — Complete Reference
School 1: OBV Flow (5 rules)
Price at/near 20-bar low (within 5% of range) — bull trigger
OBV well above its 20-bar low (>15% of OBV range) — divergence detection
OBV above its SMA(20) — volume flow trend confirmation
OBV slope accelerating (current 5-bar slope > previous) — momentum
Bull structure (higher lows) confirmed — structural context
Bear: symmetric mirror of all conditions
School 2: Confluence (9 rules — 2 trigger + 7 scored, need 4/7)
Trigger: RSI crosses above 30 (bull) or below 50 (bear)
Trigger gate: ADX ≥ 20 + price on correct side of EMA
Score: ADX ≥ 25 (strong trend)
Score: Bull/bear structure confirmed
Score: Price above/below SMA(50) (longer-term trend alignment)
Score: MACD line vs signal agreement
Score: Price touched EMA in last 2 bars (level test)
Score: Volume above average
Score: Candle body ratio > 50%
School 3: Wyckoff (9 rules — 7 standard + 2 trap events)
EMA cross initiates pullback tracking
Pullback duration ≥ 3 bars
Average pullback volume < pre-pullback average volume (declining effort)
OR average body ratio < 0.45 during pullback (narrow bars)
Bounce bar body ratio > 50% (strong commitment)
Bounce bar volume > pullback average volume (expanding effort)
EMA cross back confirms resolution
Spring: price breaks below previous swing low, closes back above with volume
Upthrust: price breaks above previous swing high, closes back below with volume
School 4: Amplitude Strength (7 scored, need 4/7)
Bull/bear structure confirmed
Trend wave amplitude > 0.8 ATR (bull: up-wave, bear: down-wave separately)
Trend wave speed > pullback speed (impulsive move, not grinding)
Pullback duration < trend wave duration (quick correction)
Current pullback shallower than previous (< 1.2x)
Current swing volume < previous swing volume (swing-to-swing comparison)
RSI < 40 at swing low (bull) / RSI > 60 at swing high (bear)
School 5: VWMA Delta (1 rule)
RMA(30) of VWMA(5) minus VWMA(30) crosses zero
School 6: Kalman Filter LQE (1 rule)
Kalman filter (length 50, R=0.01, Q=0.10) crosses above/below Kalman filter (length 100)
School 7: Naive Bayes Adaptive (6 features + confidence threshold)
Feature: 3-bar body trend (growing or shrinking candle bodies)
Feature: Wick dominance (upper vs lower wick ratio — rejection direction)
Feature: Price percentile in 20-bar range (position within recent range)
Feature: Volatility regime (ATR vs its SMA — expanding or contracting)
Feature: Momentum acceleration (bar-to-bar price change speeding up or slowing)
Feature: Gap behavior (open vs previous close, ATR-normalized)
Threshold: P(bull) ≥ 65% to vote bull, P(bull) ≤ 35% to vote bear
Requires minimum 15 resolved samples before voting
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
How the Schools Differ
Schools 1 & 5 are volume-driven — they measure where money is flowing, not where price is moving.
Schools 2 & 4 are multi-factor scoring systems — they require multiple conditions to align before voting, reducing false positives.
School 3 is event-driven — it detects specific Wyckoff structural events (springs, upthrusts, effort exhaustion) rather than continuous measurements.
School 6 is filter-driven — it uses an adaptive mathematical estimator that adjusts its own responsiveness based on estimation uncertainty.
School 7 is the only School that learns — it builds its model from the instrument's own history and adapts over time. Every other School uses fixed rules.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The Voting System
Each School votes independently. Votes are collected within a 3-bar window — Schools do not need to fire on the exact same bar to count as agreeing. This accommodates the fact that different analytical methods detect events at slightly different times.
The dashboard shows each School's most recent vote using directional emojis and colors the School name green (bull vote) or red (bear vote) when it participated in the last signal. Schools are sorted by recency — the most recently active School appears at the top of the list.
The Hit Rate column shows each School's accuracy when it participated in council signals — how often signals were correct when that School voted. This is not standalone accuracy; it measures performance within the council context.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
POC Lines (Anchored VWAP)
Three dashed lines that represent volume-weighted fair value since the last extreme volume event:
Center — the anchored VWAP: where volume-weighted price has centered since the last climax event
Upper and Lower — standard deviation bands that start at the same point as the center (origin) and branch outward as price disperses
The POC re-anchors when a volume extreme is detected (volume z-score exceeds the threshold with a directional candle). All three lines converge to a single origin point at the climax bar, then branch as the new VWAP accumulates data.
The line closest to price is highlighted with increased width and brightness. When the council signals a direction and price subsequently moves against it (crossing the POC center in the wrong direction for 3+ bars), the highlighted line changes color — red for a failed bull signal, green for a failed bear signal. This failure detection provides immediate visual feedback that the anticipated move did not materialize.
Hull smoothing can be applied to the POC lines for cleaner visual tracking.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EVWAP (Exponentially Weighted VWAP)
A solid line that tracks volume-weighted fair value with exponential decay, re-anchoring at swing direction changes:
Uses the same Exponentially Weighted Moving Average formula as the DS-VWAP methodology
Re-seeds at swing pivot points detected by the swing period setting
Volume spikes are capped at 3x the 20-bar average to prevent single bars from hijacking the calculation
Changes color based on swing direction — bull color when the most recent swing high is more recent, bear color when the most recent swing low is more recent
Direction change triangles mark where each new segment begins
Hull smoothing can be applied for a cleaner line.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The Cyclic Structure: POC within EVWAP
The POC and EVWAP operate on different cycles and anchor to different events:
EVWAP re-anchors on swing direction changes (structural pivots in price). It represents the macro fair value — where the broader trend says price should be.
POC re-anchors on volume extreme events (climax bars). It represents the micro fair value — where volume clustered after the last burst of aggressive participation.
These cycles are not synchronized. A volume climax can happen mid-swing. A swing pivot can happen without a volume extreme. When both re-anchor near the same bar, that is a structurally significant event — both macro and micro fair value are resetting simultaneously.
The POC lines oscillate within the EVWAP framework. When the POC center is above the EVWAP line, volume-weighted activity is biased above the structural trend — bullish pressure. When below, bearish pressure. This relationship provides a dynamic reading of whether short-term volume activity agrees with the broader trend direction.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Risk/Reward Boxes
When a signal fires, two boxes are drawn:
Green box (above entry for bull, below for bear) — the take-profit zone at 2:1 risk-reward ratio
Red box (below entry for bull, above for bear) — the stop-loss zone at 0.5 ATR from the signal bar's extreme
Boxes extend 15 bars forward
Higher vote counts produce slightly more opaque boxes (stronger conviction = more visible)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Hit Rate and Accuracy Tracking
The indicator tracks signal accuracy using Maximum Favorable Excursion (MFE):
After each signal, the tracker monitors the next 12 bars
If price reaches 0.5 ATR in the signal direction at any point during those 12 bars (using the bar's high for bull signals, low for bear signals), the signal is marked correct
This is not a close-at-bar-12 check — it measures whether the move occurred , not whether it held
The dashboard displays:
Per-School Hit Rate — accuracy when that School participated in the council signal
Council Accuracy — overall accuracy across all evaluated signals
Signals — evaluated count vs total fired (signals during an active evaluation window are not double-counted)
Naive Bayes Learning — current status and class distribution of the adaptive learner
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Visual Aesthetics
The indicator is designed for visual clarity on dark-themed charts:
POC lines — dashed, in a distinct blue tone, with the tracked line highlighted at double width
EVWAP line — solid, colored by swing direction (bull/bear), with direction triangles at segment starts
Climax circles — small colored dots marking extreme volume events, no glow clutter
Signal labels — directional arrows with vote counts (e.g., "↑ Up (3/7)")
Dashboard — Schools sorted by recency of last vote, with bull/bear emojis and color-coded names. Schools that voted in the most recent signal appear at the top and light up in the direction color.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Key Settings
Council Behavior — "2+ Agree" (consensus) or "All Signals" (any School)
Signal Cooldown — Minimum bars between same-direction signals (default 30). Opposite-direction signals are not blocked.
School Toggles — Enable or disable each of the 7 Schools independently.
POC/EVWAP Smoothing — Raw or Hull smoothed. Hull length configurable.
Swing Period — Controls EVWAP re-anchoring sensitivity (default 55).
Volume Lookback — Bars analyzed for climax detection and volume statistics.
NB Min Samples — Minimum resolved outcomes before the Naive Bayes School starts voting.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Disclaimer
This indicator is provided for educational and informational purposes only. It is not financial advice, and it does not constitute a recommendation to buy, sell, or hold any financial instrument.
All trading involves risk. Past performance of any signal, voting system, or analytical method does not guarantee future results. The council votes, hit rates, and accuracy statistics displayed represent computational assessments based on the indicator's rules applied to historical data loaded in PulseWire. They are not predictions and should not be treated as certainties.
The Naive Bayes School learns from the chart data currently loaded. Its learned patterns may not generalize to future market conditions, different instruments, or different timeframes. The hit rates displayed in the dashboard reflect performance on the loaded chart history only and are subject to survivorship bias, lookback bias, and data limitations inherent to backtesting on historical bars.
No indicator, algorithm, or model — regardless of how many independent methods it combines — can account for all market variables including liquidity events, news-driven gaps, exchange outages, dark pool activity, or sudden regime changes.
Traders should always use independent risk management, position sizing, and their own judgment before entering any trade.
By using this indicator, you acknowledge that you are solely responsible for your own trading decisions and that the authors accept no liability for any losses incurred.
Indicator
Automate on Hyperliquid - Strategy Webhook Template [HYPR-run]DESCRIPTION
You define the entry signal. The system manages everything after the fill. This is a production-grade trade system for automating strategies on Hyperliquid using PulseWire webhooks. Five-level priority chain trade system. Four ATR trailing architectures including volume-weighted ATR with Efficiency Ratio scaling and ratchet floor. Smart stops that exit when a trade is invalidated. Pyramid scaling into winners and a redundant failsafe stop.
Three signal systems are included ready to backtest and deploy (EMA crossover, Turtle breakout, SFP - Swing Failure Pattern) that you can toggle on/off independently; replace or extend them with your own logic in three places: the input toggle, the signal condition, and the priority chain entry call. There are clear landmarks in the code to make it as straightforward as possible.
This strategy is built for you to hit the ground running backtesting or automating with a systematic framework to execute around your entry logic or the example signals provided. All signals fire on confirmed bar closes only. Entries, exits, pyramids, and stops are evaluated at close, not during the bar, so intrabar wick spikes do not trigger the system. This is by design. No lookahead bias: all highest/lowest references use prior-bar offsets, LinReg is calculated with offset=1, and no security() calls are used. The script does not repaint or compound returns.
WHAT THE STRATEGY SYSTEMIZES
1. Five-Level Priority Action Chain
Entries fire first. Pyramids fire second and block exits on the same bar. Trailing exits ride winners. Smart stops catch failing trades early. Failsafe stop is the absolute floor. The if/else order is intentional and prevents conflicts so that every action occurs only when it should.
2. Four ATR Trailing Stop Modes
Select from a dropdown. All use separate long/short look backs and multipliers because drops are faster than rallies; the defaults reflect this asymmetry.
• A3.1: LinReg + plain ATR, no ratchet. Baseline for comparison.
• A4.0 (default): LinReg + volume-weighted ATR + Efficiency Ratio + ratchet. VWATR discounts low-volume bars. ER tightens in chop (0.8x), widens in trend (1.2x). Ratchet means the stop only moves in your favor.
• A4.1: Chandelier + VWATR + ratchet + first-bar multiplier for tighter initial protection.
• A4.2: LinReg + VWATR, no ratchet or ER. Stop moves freely with projection.
***The multipliers determine how much room the stop gives price before triggering. They have the greatest influence on overall system performance and must be tuned to the asset and timeframe being traded. Default values are a starting point, not final settings.
• L Multi: 4.0 (long stop distance). Wider because uptrends are slower and require more room.
• S Multi: 2.0 (short stop distance). Tighter because drops are faster and corrections are sharper.
• Long LB: 14 bars. ATR lookback for long stops.
• Short LB: 26 bars. ATR lookback for short stops; longer lookback smooths volatile short-side moves.
• LinReg LB: 10 bars. LinReg projection window (A3.1, A4.0, A4.2).
• First Bar Mult: 1.5x (A4.1 only). Tighter stop on the entry bar; expands to standard multiplier after.
3. Smart Stops
Two trigger paths, both requiring open P&L below threshold (default -3.5%): (1) price crosses under the trailing stop while losing, or (2) price breaks the entry bar’s structure while losing. Either path exits the trade before the failsafe would trigger. The P&L condition on both paths prevents exits on noise when the trade is still within normal range.
4. Pyramid Entries
Scales into winning trades on 5-bar extremes. Requires full bar confirmation and must be within 13 bars of the initial entry.
5. Basic Entry Quality Filters
Applied automatically to every entry:
• Wick nullification: bars with wicks > 38.2% of range block entries in that direction
• SFP nullification: active reversal patterns block opposing entries
• Full bar filter: candle body must be >= 66.6% of total range
• Bar confirmation: entries only fire on confirmed bars
THREE SIGNALS INCLUDED (replace or extend)
• XO/XU: EMA crossover with four configurable pairs (5/13, 9/26, 12/25, 26/128). Requires price above swing high (longs) or below swing low (shorts) plus volume spike (Dropdown Selection).
• Turtle: 13/26 bar breakout with Lost Trade System logic. First breakout after an opposing signal gets priority.
• SFP: Swing Failure Pattern. Longs fire on either 5/5 with full-body confirmation or 5/2 with bullish candle confirmation and strong volume spike (1.618x average). Shorts fire on 5/5 with full-body or 13/3 with bearish candle confirmation. Dual-path per direction allows the signal to catch both high-conviction structure failures and high-volume reversals. The function accepts any left/right look back combination, making it straightforward to adapt. (#/# refers to pivot look back left and right)
Each has its own toggle. Enable one, combine them, or swap in your own signals.
WEBHOOK AUTOMATION
Every fill event fires through PulseWire’s built-in webhook system when enabled: entries, exits, pyramids, smart stops, and failsafe closes. To execute those webhooks on Hyperliquid, an intermediary service (execution layer) that accepts PulseWire webhooks and routes orders to Hyperliquid's API is required.
Setup:
1. Create an alert on this strategy
2. Set trigger to "Order fills only"
3. Check Webhook URL, paste your endpoint
4. Message box: {"ticker":"{{ticker}}","position":"{{strategy.market_position}}"}
5. Set expiration to Open-ended
The snippet will most likely require customization depending on your execution layer. The {{ticker}} and {{strategy.market_position}} fields are PulseWire placeholders that auto-populate when a strategy signal fires.
We recommend referencing PulseWire’s Strategy Alerts documentation to fully understand placeholder use and function when setting up your snippet for your execution layer: www.pulsewire.com
BUILDING WITH YOUR OWN SIGNALS
The most straightforward path is adding your own entry logic. The ATR module, smart stops, and pyramids can also be edited to preferred logic while still leveraging the systemized structure for clean execution when automating on an exchange.
Option 1: Replace an existing signal. Find its section under the SIGNALS header (look for "EXAMPLE 1", "EXAMPLE 2", or "EXAMPLE 3"). Delete the example code and write your condition in its place. Find the matching entry in the STRATEGY CALLS priority chain and swap the condition variable. The toggle still works; rename its label in the input line. Everything downstream works automatically.
Option 2: Add a new signal. Three places to touch:
1. Copy a strategy toggle line from the STRATEGIES input group, change the variable name and label
2. Add your signal logic in the SIGNALS section as a boolean
3. Add an else-if block in the STRATEGY CALLS priority chain using your toggle as the gate
Two test switches (Tsw1, Tsw2) are reserved in Settings for custom signals.
READING THE CHART
Candles are colored by direction: black bodies up, gray bodies down (Quant Filter toggle).
The trailing stop draws as a colored line following your position: green below price when long, red/orange above price when short. A gradient fill shades the zone between price and the stop; it intensifies as price approaches the exit level.
Green dots on the long stop line and red dots on the short stop line are ratchet markers (A4.0 and A4.1 only). Each dot means the stop locked in a new level and will not pull back.
Entry labels appear at each fill: "xoL" (EMA long), "xuS" (EMA short), "tL" (Turtle long), "tS" (Turtle short), "sfpL"/"sfpS" (SFP entries), "pyrL"/"pyrS" (pyramid adds). Exit labels: "Cl"/"Cs" (trailing close long/short), "smrtstp" (smart stop), "fstp" (failsafe).
SFP candle wicks are color-coded by lookback: 5/5 bull wick = bright green, 5/2 bull wick = dark green, 5/5 bear wick = bright red, 13/3 bear wick = dark red. The shade tells you which configuration triggered — brighter means the more common 5/5 detection, darker means the secondary lookback fired.
Horizontal lines extending from entry price are the Late Entry Window: white solid line is entry price, green dashed line is entry + ATR window, red dashed line is entry - ATR window. Visual reference only; does not affect trade logic. Useful when away from the screen to quickly see if a missed entry is still within a safe ATR range.
Market structure labels (HH, LH, HL, LL) appear at swing pivots when the Structure toggle is enabled.
RISK MATH
Order size is fixed at $5,000 (50% of starting capital). That means it's always a flat $5k order, no compounding. With the failsafe at -5.25%, maximum loss per trade is $262.50, or 2.625% of the $10,000 starting balance.
*Because order size is fixed in dollars while equity grows, risk as a percentage of equity decreases over time: 2.625% at start, 2.1% at $12,500, 1.75% at $15,000. The smart stop triggers before the failsafe in most cases, reducing average realized loss further.
STRATEGY PROPERTIES (What's used in the chart published here)
Strategies (all off by default - toggle on to activate):
• XO/XU: on
• Turtle: on
• SFP: on
Settings:
• Mode: Historical (switch to Bot Mode for live automation - limits calculation depth for speed)
• EMA Pair: 9/26
Risk Management:
• Smart Stop: on | -3.5%
• Failsafe Stop: on | -5.25%
• Mech TP/Cls: on
ATR Trailing Exits:
• Mode: A4.0
• L Multi: 4.0 | S Multi: 2.0
• Lng LB: 14 | Shrt LB: 26
• LinReg: 10 | First Bar: 1.5 (A4.1 only)
Backtest Properties:
• Initial capital: $10,000
• Commission: 0.05%
• Slippage: 2 ticks
• Order size: $5,000 (cash, fixed)
• Fill limit assumption: 5 ticks
• Max risk per trade: $262.50 (2.625% of starting equity)
CREDITS
ATR: J. Welles Wilder (1978).
Efficiency Ratio: Perry Kaufman.
Turtle breakout concept: Richard Donchian. Strategy
FunctionSMCMCLibrary "FunctionSMCMC"
Methods to implement Markov Chain Monte Carlo Simulation (MCMC)
markov_chain(weights, actions, target_path, position, last_value) a basic implementation of the markov chain algorithm
Parameters:
weights : float array, weights of the Markov Chain.
actions : float array, actions of the Markov Chain.
target_path : float array, target path array.
position : int, index of the path.
last_value : float, base value to increment.
Returns: void, updates target array
mcmc(weights, actions, start_value, n_iterations) uses a monte carlo algorithm to simulate a markov chain at each step.
Parameters:
weights : float array, weights of the Markov Chain.
actions : float array, actions of the Markov Chain.
start_value : float, base value to start simulation.
n_iterations : integer, number of iterations to run.
Returns: float array with path. Library
Indicator
Indicator
