Skip to content
Signal Pilot

Volume Oracle - Regime Detection

Regime-based volume intelligence indicator. Detects accumulation and distribution phases through adaptive flow analysis, market structure validation, and multi-factor quality scoring.

πŸ‘‹

New to Technical Analysis? Start Here

What Is Volume Oracle?

Volume Oracle analyzes buying and selling pressure to identify market regimes : periods where institutions are accumulating (buying) or distributing (selling).

Think of it like reading the "mood" of the market:

  • ACCUMULATION = Big players buying β†’ Green regime β†’ Bullish bias
  • DISTRIBUTION = Big players selling β†’ Red regime β†’ Bearish bias
  • NEUTRAL = No clear direction β†’ Gray regime β†’ Wait for clarity

What You'll See on Your Chart:

  • Volume Bars : Green (bullish) or Red (bearish) colored by regime
  • Signal Labels : ↑ or ↓ arrows with quality stars (⭐⭐⭐)
  • Regime Table : Dashboard showing current regime status and health
  • Background Tint : Subtle green/red tint showing regime direction

How It Works (Simple Version):

  1. Analyzes volume flow over time (not just single bars)
  2. Detects when regime flips between accumulation/distribution
  3. Validates signals with market structure and multiple factors
  4. Shows quality score so you know which signals matter most
πŸŽ“ Why Regimes Matter

Regimes = The Market's Direction

Individual volume bars are noisy. Regimes smooth out the noise:

  • Strong ACCUMULATION regime = Sustained buying pressure over time, not just one bar
  • Regime FADING = Early warning that direction may change
  • Structure CONFLICT = Price action disagrees with regime β†’ be cautious

Volume Oracle helps you analyze WITH the dominant flow, not against it.

Start by watching the regime table. Learn ACCUMULATION vs DISTRIBUTION, then observe how regime changes relate to price.

πŸŽ“ Master this indicator with our free lessons: Lesson: Volume Oracle Regimes

🎯 Core Functionality Intermediate

The Volume Oracle pane on BTCUSDT.P daily across a year, showing coloured volume bars, tinted regime backgrounds, two starred signal labels and the seven-row regime table reading ACCUMULATION.
Everything the indicator draws, in one frame. The table reports the regime and its strength, then Status, Health, Struct, Market and Flip below it.
πŸ“Š

Regime State Machine

Volume Oracle tracks volume flow through three regime states:

            β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
            β”‚    NEUTRAL    β”‚
     β”Œβ”€β”€β”€β”€β”€β”€β–Ά    (Gray)    ◀──────┐
     β”‚      β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜     β”‚
     β”‚              β”‚             β”‚
  Weakens       Confirms       Weakens
     β”‚              β”‚             β”‚
     β”‚       β”Œβ”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”      β”‚
     β”‚       β–Ό             β–Ό      β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ ACCUMULATIONβ”‚     β”‚DISTRIBUTION β”‚
β”‚   (Green)   │◀───▢│   (Red)     β”‚
β”‚ Buying Flow β”‚     β”‚Selling Flow β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

State Transitions: Regime changes require confirmation bars (adaptive to timeframe). Flip counter prevents whipsaws in choppy markets. Early warnings fire BEFORE regime actually flips.

The Volume Oracle pane on BTCUSDT.P daily from October to December, mostly green volume bars on a green background tint, with a two-star up signal label on a tall green bar.
An accumulation stretch. The background tint carries the regime and the bar colours carry each session, so the two can disagree without either being wrong.
The Volume Oracle pane on BTCUSDT.P daily from July to September, mostly red volume bars on a red background tint, with a down warning label above a tall red bar.
The same view during distribution. The isolated green bars inside the red stretch are what the regime reading is there to keep in proportion.

Signal Quality Scoring

The Volume Oracle pane on BTCUSDT.P daily from October to March, with an up label carrying two stars and another up label carrying three stars and a target marker.
Two signals from the same run, rated differently. Three stars needs a score of 85 or above; two needs 75. Below 65 the signal still prints and simply earns no star.

Not all signals are equal. Volume Oracle scores each signal 0-100% based on multiple factors:

Factors Considered:

  • Volume significance relative to recent activity
  • Flow direction alignment with signal
  • Price trend confirmation
  • Current regime strength
  • Market structure agreement (HH/HL vs LH/LL patterns)
  • Volume footprint type
  • Multi-factor confluence

Dynamic Adjustments:

  • Scores adjusted higher in trending markets
  • Scores adjusted lower in choppy/ranging conditions
  • Recent signal clustering reduces individual signal scores

How the score is banded:

RatingScore
⭐65 to 74
⭐⭐75 to 84
⭐⭐⭐85 and above

Signal Generation

Signal Types:

  • 🟒 BULL Event (↑) : Bullish conditions confirmed, accumulation phase detected
  • πŸ”΄ BEAR Event (↓) : Bearish conditions confirmed, distribution phase detected

Quality Ratings (⭐): Each signal receives a 0-100% quality score displayed as stars:

RatingScoreMeaning
⭐⭐⭐85 and aboveThe strongest agreement between factors
⭐⭐75 to 84Most factors lined up
⭐65 to 74Enough to show, no more
no starunder 65The signal still fires and is still drawn. It just earns no star.

Quality Score Factors: Volume Z-score strength, flow consistency, trend alignment, regime strength

Risk Management

Auto-Calculated Levels:

  • Position Size : Based on account size, risk %, and stop distance
  • Stop Loss : ATR-based calculation (default: 1.5Γ— ATR)
  • Target 1 (T1) : First profit target (default: 2.0Γ— ATR)
  • Target 2 (T2) : Extended profit target (default: 3.5Γ— ATR)

Position Sizing Formula: Position Size = Risk Amount Γ· Stop Distance

Example: $10,000 account Γ— 1% risk = $100 risk. If stop is $50 away, position size = 2 units.

HTF Confirmation (Optional)

What It Does: Checks higher timeframes for regime alignment before firing signals.

HTF Table Display: Shows HTF1 and HTF2 regime state, strength %, and alignment status.

Benefit: Filters out signals that conflict with higher timeframe trend direction.

Strategy Modes

ModeDescriptionBest For
Trend FollowingEvents align with regime directionTrending markets, momentum analysis
Mean ReversionEvents at regime extremes (fading)Range-bound markets, contrarian analysis
HybridBoth signal types enabled at onceMixed conditions, more signals of both kinds

Timeframe Compatibility: Works on all timeframes. Signals confirm at bar close (non-repainting).

Remember: Signals fire only when multiple conditions align: a volume spike registered, flow consistency confirmed, the regime pointing the same way. The star band records how many of the scored factors were among them.


πŸ“Š The Regime Table

The Volume Oracle regime table on BTCUSDT.P daily, reading ACCUMULATION, then 100% and 456h, then Status STRONG, Health WATCH, Struct ALIGNED, Market NORMAL and Flip STABLE.
Seven rows, read top to bottom: the regime, its strength with how long it has held, then status, health, whether structure agrees, the market condition and how near the regime is to flipping.

The regime table is your dashboard for regime status. Available in two layouts:

Vertical Layout (Default)

RegimeACCUMULATION
Strength66%
Duration32h
Statusβœ“ STRONG
Health● HEALTHY
Structureβœ“ ALIGNED
MarketTRENDING
Flipβœ“ STABLE

Horizontal Layout

ACCUMULATION 66% 32h STRONG βœ“ ●
STRUCTURE βœ“ MARKET
TRENDβ–²
FLIP
STABLE
0 flips

Table Fields Explained

FieldValuesMeaning
RegimeACCUMULATION / DISTRIBUTION / NEUTRALCurrent volume flow direction
Strength0-100%How dominant is the current regime
DurationHours (e.g., 32h)How long regime has been active
StatusSTRONG βœ“ / FADING β–Ό / WEAK βœ— / FLIP ⟲Regime health indicator
Health🟒 🟑 🟠 πŸ”΄How many warning flags are up: none, one, two, three or more
Structureβœ“ ALIGNED / βœ— CONFLICT / β€” UNCLEARDoes price structure confirm regime?
MarketTRENDING β–² / NORMAL β€” / CHOPPY β–ΌMarket character based on flip frequency
FlipSTABLE βœ“ / β†’ ACC 2/3 / β†’ DIST 1/3Is regime about to change?

Reading the Table

Ideal Bullish Setup:

  • Regime: ACCUMULATION
  • Status: STRONG βœ“
  • Health: 🟒
  • Structure: βœ“ ALIGNED
  • Market: TRENDING β–²
  • Flip: STABLE βœ“

Warning Signs:

  • Status: FADING or WEAK β†’ Regime losing strength
  • Health: 🟠 or πŸ”΄ β†’ Multiple warning flags
  • Structure: βœ— CONFLICT β†’ Price disagrees with regime
  • Market: CHOPPY β†’ Unreliable signals
  • Flip: β†’ DIST 2/3 β†’ About to flip bearish

πŸ“Š Backend Systems

Volume Oracle includes five intelligent backend systems that work automatically:

1. Market Structure Detection

Analyzes swing highs and lows to determine if price structure confirms or conflicts with the current regime.

StructureMeaning
BULLISHUptrend structure (higher highs/lows)
BEARISHDowntrend structure (lower highs/lows)
MIXEDTransitioning between states
UNCLEARRanging or choppy price action

Impact: Signals receive quality bonus when structure aligns with regime direction, penalty when conflicting.

2. Volume Footprint Detection

Classifies volume bars by their characteristics to identify significant volume patterns:

TypeCharacteristics
MOMENTUMHigh volume with strong directional conviction
ABSORPTIONHigh volume with price containment (supply/demand absorbed)
SPIKEElevated volume without clear directional signature
NORMALTypical volume activity

Impact: Quality scoring adjusts based on footprint type alignment with signal direction.

3. Regime Stability Index

Tracks regime flip frequency over a rolling window to characterize market conditions:

CharacterMeaning
TRENDINGStable regime, few recent flips
NORMALModerate regime stability
CHOPPYFrequent regime changes

Impact: Signal quality expectations automatically adjust based on market character.

4. Confluence Scoring

Evaluates how many independent factors support each signal:

Factors Evaluated:

  • Volume spike presence
  • Flow direction match
  • Structure agreement
  • HTF alignment (if enabled)
  • Footprint confirmation
  • Market character
  • Regime strength

Impact: Each factor that lines up adds to the score, and four or more together add a further bonus of 5 to 15 points.

5. Signal Density Tracking

Monitors signal frequency in recent bars to identify potentially choppy conditions.

Impact: When many signals cluster together, individual signal quality is reduced to reflect lower reliability in choppy markets.


βš™οΈ Settings

The Volume Oracle settings dialog on the Inputs tab, showing Detection with Volume spike threshold, Regime confirmation bars, Regime sensitivity, Auto-adapt to volatility and Regime warnings, and Risk with Account size, Risk per trade, ATR length, Stop and Target 1.
The detection group decides what counts as a spike and how long a regime has to hold before it is called. The risk values below it feed the sizing readout in the signal tooltip and change nothing about detection.
The same dialog scrolled to Display and Table Style, showing MTF threshold, Regime table, Regime background, Exit warnings, Quality stars, TUBE labels, Line in tooltips, Size in tooltips and HTF table, with Layout, Position and Text size below.
Quality stars and the regime background can each be turned off without affecting the underlying reading. Layout, Position and Text size only move the table.

1️⃣ Detection

SettingDefaultDescription
Volume spike threshold2.0The z-score a bar's log volume must reach, measured over 100 bars. Raising it lets fewer bars through
Signal cooldown (bars)45Minimum bars between signals
Regime sensitivityBalancedConservative/Balanced/Aggressive
Auto-adapt to volatilityβœ“ OnAdjusts thresholds automatically
Regime warningsβœ“ OnShow early warning when regime weakening

2️⃣ Risk

SettingDefaultDescription
Account size ($)10,000For position sizing calculation
Risk per trade (%)1.0% of account to risk
ATR length14For stop/target calculations
Stop (ATRΓ—)1.5Stop loss distance
Target 1 (ATRΓ—)2.0First profit target
Target 2 (ATRΓ—)3.5Second profit target
Partial exit at T1 (%)50Position % to close at T1
Trailing stopβœ“ OnTrail after T1 hit
Trailing (ATRΓ—)1.0Trailing stop distance
Breakeven (ATRΓ—)1.0Where the BE marker is placed, in ATR from entry

3️⃣ Multi-Timeframe

SettingDefaultDescription
Enable HTF filterOffRequire HTF alignment
HTF 160 (1H)Primary higher timeframe
Enable HTF 2OffSecond HTF filter
HTF 2240 (4H)Secondary higher timeframe
Strict modeβœ“ OnHide signals when HTF disagrees
Min HTF strength (%)40Required HTF regime strength

4️⃣ Strategy

SettingDefaultDescription
ModeTrend FollowingTrend Following / Mean Reversion / Hybrid
Mean reversion signalsOffShow counter-trend signals at extremes
MR threshold2.5How extreme for MR signal

5️⃣ Display

SettingDefaultDescription
Regime tableβœ“ OnShow regime dashboard
Regime backgroundβœ“ OnTint chart background
Exit warningsβœ“ OnShow ⚠️ labels
Quality starsβœ“ OnShow ⭐ on signals
T1/BE labelsOffShow management labels (clutters chart)
Risk in tooltipsβœ“ OnShow stop/targets in tooltips
Size in tooltipsβœ“ OnShow position size in tooltips
HTF tableβœ“ OnShow HTF panel when enabled

6️⃣ Table Style

SettingDefaultDescription
LayoutVerticalHorizontal or Vertical
PositionBottom Right9 position options
Text sizeTinyTiny/Small/Normal/Large
Transparency850=solid, 100=invisible
Border1Border width 0-3
Frame0Outer frame 0-3
HTF positionBottom CenterHTF table position
HTF text sizeTinyHTF table text size

πŸ”” Alerts (25 in total)

Entry Alerts

AlertFires When
🟒 BULL SignalBullish flow signal generated
πŸ”΄ BEAR SignalBearish flow signal generated
⚑ ANY SignalEither direction signal

Position Alerts

AlertFires When
🎯 Target 1 HitPrice reaches T1
πŸ”’ BreakevenStop moved to entry
⚠️ Exit WarningAny exit condition triggered

Regime Alerts

AlertFires When
πŸ“ˆ Regime β†’ AccumulationRegime flips bullish
πŸ“‰ Regime β†’ DistributionRegime flips bearish
βš–οΈ Regime β†’ NeutralRegime becomes neutral
πŸ”„ Any Regime ChangeAny regime flip
⚑ Regime WeakeningRegime losing strength
πŸ“‰ Momentum FadingMomentum losing strength inside the regime
πŸ“‰ Flow DeterioratingFlow turning against the regime
πŸ“‰ Volume Drying UpParticipation falling away
🟠 Multiple WarningsMore than one of the warnings above active at once

Structure Alerts (NEW)

AlertFires When
πŸ“Š Structure BullishHH/HL pattern detected
πŸ“Š Structure BearishLH/LL pattern detected
⚠️ Structure ConflictStructure disagrees with regime

Footprint Alerts (NEW)

AlertFires When
πŸ”₯ Momentum FootprintStrong directional momentum detected
πŸ›‘οΈ Absorption FootprintSupply/demand absorption detected

Market Alerts (NEW)

AlertFires When
πŸ“ˆ Market TrendingLow flip frequency detected
πŸ“‰ Market ChoppyHigh flip frequency detected

Confluence Alert (NEW)

AlertFires When
🎯 High Confluence Signal5+ factors align on signal

HTF Alerts

AlertFires When
βœ… HTF AlignedAll timeframes agree
❌ HTF BrokeAlignment lost

Alert Message Format

Events include full analysis data:

🟒 BULLISH FLOW | BTCUSD 15m
Quality: 88% ⭐⭐⭐ | Regime: 67%
Entry: 94,000 | Stop: 92,800
T1: 95,600 | T2: 96,800
Size: 0.083 BTC | Risk: $100
Structure: βœ“ ALIGNED | Market: TRENDING

πŸ“– How to Use

Step 1: Check Regime State

Before any trade, look at the regime table:

RegimeBiasWhat it reports
ACCUMULATION + STRONGBullishBullish events favored
DISTRIBUTION + STRONGBearishBearish events favored
NEUTRALNoneNo direction detected
Any + FADING/WEAKCautionThe regime in place is losing strength

Step 2: Validate with Structure

Check if price structure confirms regime:

StructureRegimeWhat it reports
βœ“ ALIGNEDAnyStructure and regime agree
β€” UNCLEARAnyStructure gives no reading either way
βœ— CONFLICTAnyStructure and regime disagree

Step 3: Consider Market Character

MarketWhat the reading means
TRENDINGDirectional persistence detected in the volume series
NORMALNeither persistence nor unusual reversion detected
CHOPPYFrequent direction changes, so the regime reading is less stable

Step 4: Wait for Signal

When ↑ or ↓ signal appears:

  1. Check star rating (prefer ⭐⭐ or ⭐⭐⭐)
  2. Hover for tooltip (stop, targets, size)
  3. Verify regime still supports direction
  4. Enter if all factors align

Step 5: Manage Position

LabelMeaningWhat the marker records
T1Target 1 hitPrice reached the first computed target
BEBreakeven levelPrice reached the entry price again
⚠️Exit warningThe regime meter raised a warning

πŸ”— Integration with Other Indicators

πŸ’‘ Volume Oracle Works Best in Combination

While Volume Oracle reports a regime and generates signals on its own, reading it alongside the other Signal Pilot indicators gives a reading more than one source. Here is how they are commonly read together:

Volume Oracle + Pentarch (Regime + Timing)

Workflow:

  1. Pentarch event fires β†’ TD, IGN, CAP, or WRN event appears on chart
  2. Check Volume Oracle regime β†’ Is the regime aligned with the Pentarch event direction?
  3. Pentarch + Accumulation regime = validated bullish β†’ Regime confirms volume support for reversal
  4. Pentarch + conflicting regime = proceed with caution β†’ Signal without regime support may lack follow-through
  5. Expected outcome: Volume Oracle regime validates which Pentarch events have volume confirmation

Example: Pentarch TD event fires β†’ Volume Oracle shows Accumulation regime (green, 75%) = confirmed bullish reversal with accumulation flow

Volume Oracle + Janus Atlas (Regime at Levels)

Workflow:

  1. Price approaches a key level drawn by Janus Atlas β†’ Daily High/Low, Weekly levels, POC, VWAP, or Fibonacci levels
  2. Check Volume Oracle regime at level β†’ What is the regime showing when price tests the level?
  3. Regime alignment at level = significance confirmed:
    • Accumulation regime + support level = strong bounce potential
    • Distribution regime + resistance level = strong rejection potential
  4. Expected outcome: Volume Oracle regime shows whether the levels drawn by Janus Atlas have volume confirmation

Example: Price hits Daily Low + Weekly Low confluence β†’ Volume Oracle shows Accumulation regime (green, 72%) β†’ price bounces = confirmed support zone with accumulation

Volume Oracle + Harmonic Oscillator (Regime + Momentum)

Workflow:

  1. Harmonic Oscillator shows momentum shift β†’ a bearish regime turning bullish, or a TRENDINGβ–² label appearing
  2. Check Volume Oracle regime β†’ Is the regime aligned with the momentum direction?
  3. Regime and momentum agreeing = two sources, not one:
    • Bull momentum + Accumulation regime = confirmed bullish momentum
    • Bear momentum + Distribution regime = confirmed bearish momentum
  4. Conflicting regime = lower confluence β†’ May lack volume participation, lower confidence

Example: Harmonic Oscillator prints TRENDINGβ–² on 7 of 7 votes β†’ Volume Oracle shows Accumulation regime (green, 80%) = maximum bullish confluence (momentum + regime)

Volume Oracle + OmniDeck (Regime at Exhaustion Counter)

Workflow:

  1. OmniDeck Exhaustion Counter completes its count β†’ the number 9 appears (buy or sell count completion)
  2. Check Volume Oracle regime at completion β†’ What regime is showing at the exhaustion point?
  3. Exhaustion Counter + aligned regime = validated exhaustion:
    • EC buy completion + Accumulation regime = bullish reversal confirmed
    • EC sell completion + Distribution regime = bearish reversal confirmed
  4. Expected outcome: Volume Oracle regime tells a real Exhaustion Counter completion from a false one

Example: OmniDeck Exhaustion Counter completes a sell count, printing the number 9 above the bar β†’ Volume Oracle shows a Distribution regime (red, 78%): two instruments describing the same bar

Pro Tip: The Regime Confirmation Workflow

For highest-confluence setups, use Volume Oracle as the regime confirmation layer. Workflow: Janus Atlas (identify level) β†’ Pentarch (timing event) β†’ Volume Oracle (regime confirmation). Price at key level + timing event + aligned regime = triple-confluence setup with volume validation. Always ask: "Is the regime supporting this setup?"

See also: Analysis Workflow Guide for detailed multi-indicator approaches.


πŸ“Š Volume Oracle vs Plutus Flow : Which One?

πŸ’‘ Both Are Volume Indicators - But Serve Different Purposes

Volume Oracle and Plutus Flow analyze volume differently. Here's how to choose:

Quick Comparison Table

Feature Volume Oracle v1.0 Plutus Flow v1.0
Primary Focus Regime detection + signal generation Cumulative volume trend analysis (OBV-based)
Best For Intraday analysis, event detection with risk analysis Multi-day analysis, trend following, divergence detection
Timeframe 5m, 15m, 1H (intraday timeframes) 1H, 4H, Daily, Weekly (higher timeframes)
Key Signal BULL/BEAR signals with quality ratings Bullish/Bearish divergence (price vs OBV)
Trend Type Regime-based (Accumulation/Distribution) Long-term money flow direction
Volume Analysis Regime-based (market phase detection) Cumulative (running total of volume)
Works Best In All market conditions (including ranging) Trending markets (uptrends/downtrends)
Unique Feature Auto risk management (Entry/Stop/Targets) OBV trend ribbons (show trend strength)

βœ… Use Volume Oracle When:

  • You're doing intraday analysis (analyzing shorter timeframes)
  • You want regime-based context (align with Accumulation/Distribution phases)
  • You want the score banded on the chart (⭐⭐⭐ from 85, ⭐⭐ from 75, ⭐ from 65)
  • You want automatic risk levels (Entry, Stop, T1, T2 calculated for you)
  • You use HTF confirmation (ensure higher timeframe agrees)

Example Volume Oracle Setup: S&P 500 15-minute chart, waiting for BULL event with ⭐⭐⭐ quality during Accumulation regime.

βœ… Use Plutus Flow When:

  • You're doing multi-day analysis (analyzing over days/weeks)
  • You want to track long-term money flow (is money flowing in or out over time?)
  • You analyze divergences (price makes new low, but OBV makes higher low = accumulation)
  • You focus on higher timeframes (Daily, Weekly charts)
  • You want trend confirmation (ribbon width shows trend strength)

Example Plutus Flow Setup: Bitcoin Daily chart, looking for bullish OBV divergence to identify potential reversals.

πŸ”₯ Use Both Together (Advanced)

Combine Volume Oracle (tactical) with Plutus Flow (strategic) for maximum effectiveness:

  1. Plutus Flow β†’ Identifies long-term trend direction (OBV rising = bullish bias)
  2. Volume Oracle β†’ Finds tactical confluence points (BULL event during Accumulation regime)

Example Combined Workflow:

  • Check Daily Plutus Flow: OBV trending up (bullish long-term)
  • Drop to 15m chart with Volume Oracle: Wait for BULL ⭐⭐⭐ event during Accumulation regime
  • Both align: Long-term bullish flow + regime-confirmed event = high-confluence setup

πŸ’‘ Pro Tip: Choose Based on Your Analysis Style

Intraday analysis: Volume Oracle is your primary volume tool. Add Plutus Flow optionally for daily bias.

Multi-day analysis: Plutus Flow is your primary volume tool. Add Volume Oracle optionally for confirmation.

Position analysis: Plutus Flow on Weekly/Monthly charts for long-term trend direction.

See also: Plutus Flow Documentation for comparison from the other perspective.


⚠️ Common Mistakes

Mistake #1: Acting Against Regime

Missed: reading a bullish event in a DISTRIBUTION regime as though the regime agreed

Read: the event and the regime disagree, and both are on screen

Mistake #2: Ignoring Structure Conflicts

Missed: reading a signal as though nothing disagreed, when Structure shows βœ— CONFLICT

Read: the structure and the regime disagree, so the reading has one source rather than two

Mistake #3: Expecting Results in CHOPPY Markets

Missed: reading a CHOPPY market the same way as a TRENDING one

Read: CHOPPY is the market character the indicator detected, and it is printed before anything happens

Mistake #4: Reading Every Band the Same Way

Missed: reading every ⭐ event as though it were a ⭐⭐⭐

Read: the star band is the score put into bands, and it is printed next to the signal

Mistake #5: Ignoring Early Warnings

Missed: leaving a reading unchanged when Status shows FADING

Read: FADING is the meter revising itself, so the reading it was built on has changed


🌫️ When This Doesn't Work Well

Low Volume Sessions

Holiday trading, overnight sessions: regime detection less reliable when volume baseline is low.

Major News Events

Fed announcements, earnings: regime can flip multiple times in minutes. Wait for stabilization.

Choppy/Ranging Markets

When the Market row reads CHOPPY often, the regime input the scoring leans on is itself unsettled, and the scores reflect that.

Very Low Timeframes

On 1m and 3m charts the volume z-score is computed over 100 very short bars, so more signals clear the threshold and fewer of them reach the upper bands. The scoring rests on steadier inputs from 5m upward.


❓ FAQ

Q: Does this repaint?

A: No. All signals fire on bar close only. Historical signals match live behavior.

Q: What timeframes work best?

A: 5m to Daily. The indicator auto-adapts parameters to each timeframe.

Q: Should I use HTF filter?

A: Optional. The filter drops signals whose higher-timeframe regime disagrees, so fewer print and the ones that do carry that agreement. Read the chart both ways to see the difference.

Q: Where do the star bands fall?

A: At 65, 75 and 85 on the 0-100 score. A signal scoring under 65 still fires and is still drawn; it just carries no star.

Q: How do I know when to exit?

A: Watch for ⚠️ exit warnings, Status turning FADING/WEAK, or Structure conflict.


βœ… Knowledge Check

Question: How many main systems make up Volume Oracle?


πŸ“‹ Quick Reference

Regime States

Regime Color Bias
ACCUMULATION Green Bullish
DISTRIBUTION Red Bearish
NEUTRAL Gray None

Status Meanings

Status Meaning
STRONG βœ“ Regime healthy
FADING β–Ό Early warning
WEAK βœ— Exit soon
FLIP ⟲ Regime changing

Health Icons

Icon Flags Meaning
🟒 No flags None of the four raised
🟑 One flag Watch it
🟠 Two flags Weakening
πŸ”΄ Three or more All but one of the four raised

Quality Stars

Stars Score Action
⭐⭐⭐ 85 and above The suggested size in the tooltip is multiplied by 1.5
⭐⭐ 75 to 84 Multiplied by 1.2
⭐ 65 to 74 Left as calculated
no star under 65 Multiplied by 0.7

Market Character

Character Meaning
TRENDING Hold winners longer
NORMAL Standard management
CHOPPY Signals resolve quickly in both directions

πŸ“ž Support

Technical Questions: support@signalpilot.io

πŸ“š Further Reading

Deepen your understanding with these articles from the Signal Pilot Blog:


πŸ’¬ Need Help?

Have questions about Volume Oracle? Join our Discord community to get help from experienced users, share setups, and discuss approaches!


See Also

Related Pages:

πŸ“Š

Master Volume Analysis the Right Way

Advanced Learning Guide includes: Volume flow analysis psychology, regime detection strategies, accumulation and distribution tracking, decision frameworks, and common mistakes to avoid

πŸ“– Open Learning Guide β†’
⏱️ 12-15 minute read

Disclaimer: Volume Oracle uses a Regime State Machine (ACCUMULATION, DISTRIBUTION, NEUTRAL) powered by five backend systems: Market Structure Detection, Volume Footprint Detection, Regime Stability Index, Confluence Scoring, and Signal Density Tracking. All analyses represent historical volume data interpretation. Risk levels are calculated automatically but exclude fees, commissions, and slippage. Individual interpretation, application, and outcomes vary. Past performance does not guarantee future results. This is not financial advice.


Educator? Earn 15–30% recurring commissions. Learn more β†’