ORACLE USER MANUAL

1. About This Manual

This manual describes Oracle — a TradingView PineScript v6 indicator that extends the multi-oscillator concept found in its sibling indicator Omnia by adding a full multi-timeframe (MTF) dimension. Where Omnia holds five oscillators on one timeframe and optionally blends them into a composite (MASH), Oracle holds five oscillators on four simultaneous timeframes — chart TF plus three configurable higher timeframes — and provides two levels of aggregation: Mash-Up (oscillator consensus within each timeframe) and Crunch (timeframe consensus across all four Mash-Ups). The result is a single number — the Crunch — that simultaneously accounts for the state of multiple oscillators across multiple timeframes.

Like Omnia, everything defaults to off. Every plot requires an explicit toggle; the default state produces a clean empty pane, not a cluttered one.

The manual is organized in the order most users will need information:

Section 2 explains the four-layer conceptual hierarchy: individual oscillators, MTF Composites, Mash-Ups, and Crunch.
Section 3 covers the five oscillators.
Section 4 covers the Auto Timeframe system.
Section 5 walks through setup and reading the output.
Section 6 is the complete settings reference.
Sections 7–9 cover practical workflows, troubleshooting, and design notes.

Quick Start

Apply Oracle to any TradingView chart. The indicator draws in a separate pane, scaled 0-100 with reference lines at 20, 50, and 80.
All plots default to off. Open settings and decide what you want to see. The quickest useful output: enable Plot Crunch in the Crunch group. This plots one line — the ultimate composite of all oscillators across all four timeframes. Most users start here.
Enable Plot Mash-Up for one or more TFs to see the per-timeframe consensus. Enable individual oscillator plots to see the underlying data.
The Auto TimeFrame system automatically assigns TF2, TF3, and TF4 based on TF1 (the chart). On a 1H chart, defaults are TF2=2H, TF3=3H, TF4=4H. Leave auto-TF on until you understand the defaults, then override specific TFs as needed.

2. Oracle’s Four-Layer Hierarchy

Oracle’s architecture is best understood as a pyramid with four levels. Each level aggregates the one below it. The Crunch at the top is the most synthesized read; individual oscillator lines at the bottom are the most granular.

Level 1 — Individual Oscillators on Each TF

Five oscillators (CMO, CRSI, RSI, Stochastic, Stoch RSI) are computed independently on each of four timeframes: TF1 (the chart), TF2, TF3, and TF4. That’s up to 20 individual series — each oscillator on each TF. Every one can be plotted independently.

At this level, the analyst sees what each oscillator says about each timeframe in isolation. RSI on TF1 might say 65 while RSI on TF4 says 42. The divergence between TFs on the same oscillator is informative on its own.

Level 2 — MTF Composite (Per-Oscillator)

For each oscillator, a weighted average across TF1-TF4 is computed using the TF weights — the “Default Weight” per timeframe in Global Settings. This produces one number per oscillator that blends its four timeframe readings.

Example: RSI TF1=65, TF2=55, TF3=50, TF4=42. If all TF weights are equal, RSI MTF Composite = (65+55+50+42)/4 = 53. The single composite RSI represents the oscillator’s overall view across timeframes.

Each oscillator’s MTF Composite can be plotted individually.

Level 3 — Mash-Up (Per-TF)

For each timeframe, a weighted average across the five oscillators is computed using the oscillator weights — the “Weight” per oscillator in each oscillator’s settings group. This produces one number per TF that blends the oscillator readings at that TF.

Example on TF2: CMO=45, CRSI=60, RSI=55, Stoch=70, Stoch RSI=65. If all oscillator weights are equal, Mash-Up TF2 = (45+60+55+70+65)/5 = 59. The Mash-Up for TF2 represents the consensus of all five oscillators at that timeframe.

There are four Mash-Ups (one per TF), each independently plottable. Optional SMA smoothing can be applied to each Mash-Up line before plotting.

Level 4 — Crunch (The Summary)

The Crunch is a TF-weighted average of the four Mash-Ups, optionally smoothed:

Crunch = sma( (Mash-Up TF1 × Weight_TF1 + Mash-Up TF2 × Weight_TF2 + Mash-Up TF3 × Weight_TF3 + Mash-Up TF4 × Weight_TF4) / (Weight_TF1 + Weight_TF2 + Weight_TF3 + Weight_TF4), Smoothing)

With all TF weights equal and smoothing = 1 (no smoothing), Crunch is simply the unweighted average of all four Mash-Ups. Increasing TF weights for higher timeframes biases the Crunch toward longer-horizon context. Smoothing reduces noise at the cost of lag.

The Crunch is the most actionable single output — it captures where multiple oscillators and multiple timeframes agree or disagree simultaneously. When Crunch is above 80, the broad multi-TF, multi-oscillator picture is bullish. When below 20, broadly bearish. Between 20 and 80, mixed or transitioning.

The Two Aggregation Dimensions

Oracle has two independent aggregation axes:

Across oscillators within a TF → Mash-Up (Level 3).
Across TFs → Crunch (Level 4, built from Mash-Ups) or MTF Composite (Level 2, built from individual oscillators).

These are computed separately — you can use either or both. Mash-Up tells you the oscillator consensus at each horizon independently. MTF Composite tells you how one oscillator looks across all horizons. Crunch combines both aggregations into a single signal.

3. The Five Oscillators

Oracle includes five oscillators — the same five as Omnia minus MFI and ADX, which aren’t in Oracle. Each runs on all four timeframes and contributes to the Mash-Up and Crunch via its oscillator Weight setting. Section references in this manual assume familiarity with each oscillator’s basic mechanics; brief descriptions follow.

Chande Momentum Oscillator (CMO)

Measures pure momentum as the ratio of total gains to total absolute movement over the lookback window. Native scale -100 to +100; Oracle rescales to 0-100 for pane compatibility. More responsive than RSI (no Wilder smoothing). Default lookback uses the TF’s Default Length.

Connors RSI (CRSI)

A composite of three sub-components: price RSI, RSI of an up/down streak counter, and percent-rank of 1-bar rate-of-change. The three are averaged to produce a 0-100 result. Designed for short-term mean-reversion sensitivity. Default RSI length uses TF’s Default Length; UpDown length can be overridden separately per TF.

RSI with Optional MA Overlay

Standard Wilder’s RSI at the TF’s Default Length. An optional moving-average overlay (SMA, EMA, RMA, WMA, or VWMA) can be added on top of the RSI line. The RSI MA is plotted as a separate line from the raw RSI. Both the RSI and RSIMA have their own MTF Composites. MA type and MA length are configurable globally (one type/length applies to all TFs and the overlay across all TFs uses the same type).

Stochastic

Standard Stochastic %K and %D. %K at the TF’s Default Length, smoothed by the global %K smoothing. %D is an SMA of %K smoothed by the global %D smoothing. Both have separate MTF Composites. Stochastic always uses close/high/low from the candle — it’s not affected by the Global Source setting.

Stochastic RSI

Stochastic applied to RSI values. RSI is first computed over the RSI length, then Stochastic %K and %D are computed over the Stoch length on the RSI series. Both %K and %D have separate MTF Composites. Default lengths use TF’s Default Length for both the RSI and Stoch windows; each can be overridden per TF.

Oscillator Weights

Each oscillator has one Weight setting (a single number across all TFs) that controls its contribution to the Mash-Up formula. Weight 0 removes the oscillator from all Mash-Up and Crunch calculations. Weight 2 makes it twice as influential as an oscillator with Weight 1.

Unlike Omnia where oscillators default to weight 0 and must be explicitly activated, Oracle applies the weight directly to the Mash-Up formula. An oscillator with Weight 0 contributes nothing to the Mash-Up even if its individual plots are enabled — plotting and Mash-Up contribution are independent settings.

4. The Auto TimeFrame System

Oracle’s Auto TimeFrame (Auto-TF) system automatically assigns TF2, TF3, and TF4 based on the chart’s current timeframe (TF1). The goal is to maintain a proportional relationship between the four timeframes — each higher TF being meaningfully larger than TF1 but not so large that it becomes unresponsive.

How It Works

For each chart timeframe Oracle recognizes (5m, 15m, 30m, 1H, 2H, 3H, 4H, 6H, 12H, 1D, 2D, 3D), the Auto-TF group has three dropdown settings: what to use for TF2, TF3, and TF4. The user selects the values they want per chart TF; Oracle picks the right row at runtime based on what timeframe the chart is currently on.

Default Auto-TF mappings (a representative sample):

Chart = 5m: TF2 = 15m, TF3 = 30m, TF4 = 1H
Chart = 15m: TF2 = 30m, TF3 = 1H, TF4 = 90m
Chart = 1H: TF2 = 2H, TF3 = 3H, TF4 = 4H
Chart = 4H: TF2 = 8H, TF3 = 12H, TF4 = 1D
Chart = 1D: TF2 = 2D, TF3 = 3D, TF4 = 5D

Each dropdown has constrained options (not every timeframe is offered for every TF slot) to prevent meaningless configurations like TF2 = 1D when the chart is on 1H (too large) or TF2 = 5m when the chart is on 1H (too small).

Overriding Auto-TF

Each TF2, TF3, and TF4 group has a “Disable Auto-TF Selection & Set TF to” toggle. When on, that TF uses the manually-configured timeframe instead of the auto-derived one. TF1 is always the chart’s timeframe and cannot be overridden.

Use the override when: you want a specific TF that isn’t in the auto-TF options; you want all four TFs to stay fixed regardless of which chart timeframe you’re on; you’re comparing the same indicator configuration across different charts and need consistency.

Which TFs Are Recognized

The auto-TF system recognizes 12 chart timeframes: 5m, 15m, 30m, 1H, 2H, 3H, 4H, 6H, 12H, 1D, 2D, 3D. Timeframes not in this list (e.g., 10m, 45m, 1W, 1M) fall back to the manual TF setting. If you use an unusual timeframe and want auto-TF to work, switch to a manual override.

Default Length per TF

Each timeframe has its own “Default Length” (used by all oscillators unless that oscillator has a per-TF length override enabled). TF1 defaults to 12; TF2 defaults to 12; TF3 defaults to 12; TF4 defaults to 12. All four are independent — raise TF4’s Default Length to 20 if you want the higher-TF oscillators to be slower without touching the lower-TF computations.

TF Weights

Each timeframe has a “Default Weight” that controls its contribution to the Crunch formula (and MTF Composites). All four default to Weight 1 — equal contribution. Raise TF4’s weight to 2 to bias the Crunch toward the longest horizon. Lower TF1’s weight to 0.5 to reduce the chart TF’s influence on the composite.

TF weights and oscillator weights are completely independent. TF weights affect how the Mash-Ups combine into the Crunch and how individual oscillator TFs combine into MTF Composites. Oscillator weights affect how oscillators combine within each Mash-Up.

5. Setup and Reading the Output

Installation

Oracle is a TradingView PineScript v6 indicator. Install via TradingView’s standard indicator-management workflow — copy the source into the Pine Editor and click “Add to Chart”.

The Pane

Oracle draws in a separate pane below the price chart. The pane is scaled 0-100 with three reference lines: Hi at 80 (dashed, semi-transparent), Mid at 50, and Lo at 20. Invisible reference lines at 0 and 100 bound the extremes.

All oscillators and composites that Oracle plots are on this shared 0-100 scale — CMO (originally -100 to +100) is rescaled; RSI, Stochastic, Stoch RSI, and CRSI are natively 0-100.

Bar-State Toggle

The Global Settings group has a Plotting Bar-State toggle:

Real Time (default) — plots update on every incoming tick, including unconfirmed live bars. Values on the current bar may change as new ticks arrive.
Confirmed — plots update only on confirmed (closed) bars. The live bar shows na until it closes. No repainting; useful for strategies where the live bar’s oscillator value mustn’t flicker.

Reading What You See

Above 80 on the 0-100 scale is the conventionally “overbought” zone. Below 20 is “oversold.” Above 50 is broadly bullish momentum; below 50 is broadly bearish. The midline at 50 is the reference equilibrium — crossing it in either direction is a momentum shift.

For the Crunch specifically: above 80 means the broad multi-TF, multi-oscillator picture is stretched to the bullish extreme. Below 20 means the same for bearish. Between 20 and 80 is the normal operating range.

For Mash-Ups: each TF’s Mash-Up tells you the oscillator consensus at that horizon. All four Mash-Ups above 80 = broad agreement on overbought across all timeframes. TF1 Mash-Up above 80 while TF4 Mash-Up is at 40 = short-term overbought with longer-term neutral — a much more cautious reading than the number at face value implies.

6. Settings Reference

Oracle’s settings are organized into 13 groups: Global Settings, four Timeframe Settings (TF1-TF4), five Oscillator groups (CMO, CRSI, RSI, Stochastic, Stoch RSI), Mash-Up, Crunch, and Auto TimeFrame. The reference below covers each group.

Global Settings

Source (Global) Default: close

Default price source for all oscillators that take a price input (CMO, CRSI, RSI, Stoch RSI). Any TradingView source is valid: open, high, low, close, hl2, hlc3, ohlc4, or any custom series.

Each oscillator group has a Source Override option — when enabled for a specific oscillator, that oscillator uses its own source instead of this global one. Stochastic always uses close/high/low by definition and ignores this setting.

Plotting Bar-State Default: Real Time

Controls whether plots include the current (unconfirmed) live bar.

Real Time: all plots update on every tick. The live bar’s values may change as new ticks arrive.

Confirmed: plots appear only on confirmed (closed) bars. The live bar shows nothing until it closes. No flickering or repainting — useful when accuracy of the final bar value matters more than real-time feedback.

1st–4th Timeframe Settings (TF1–TF4)

Four identical groups, one per timeframe. TF1 is always the chart’s timeframe (no override possible). TF2-TF4 can use Auto-TF or a manual override.

Disable Auto-TF Selection & Set TF to (TF2/TF3/TF4 only) Default: Off

When off (default), this TF uses the Auto TimeFrame mapping based on the chart’s current period.

When on, the inline timeframe picker becomes active and the manually-selected timeframe is used regardless of the chart’s period.

TF1 has no such toggle — it is always the chart’s timeframe.

Default Length Default: 12 (all TFs)

The lookback period used by every oscillator on this TF, unless that oscillator has its own length override enabled.

Increase for smoother, slower oscillators on this TF; decrease for more responsive but noisier ones.

The same default length applies across all five oscillators for this TF simultaneously. Per-oscillator overrides in each oscillator’s group can break this coupling.

Default Weight Default: 1 (all TFs)

This TF’s contribution weight in the Crunch formula and in each oscillator’s MTF Composite. All TFs default to 1 — equal contribution.

Raise to bias aggregations toward this TF. Lower to reduce its influence. Set to 0 to exclude this TF entirely from all aggregated outputs (individual plots still work).

Maximum 12.

Oscillator Groups (CMO, CRSI, RSI, Stochastic, Stoch RSI)

Each of the five oscillator groups has the same structural layout, with some oscillator-specific variations. The structure below applies to all five; oscillator-specific notes follow.

Weight of [Oscillator] In Mash-Up / Crunch Default: 0 (all oscillators)

This oscillator’s contribution to the Mash-Up formula across all TFs. 0 = excluded from Mash-Up and Crunch. Any positive value includes it proportionally.

All oscillator weights default to 0 — none contribute to the Mash-Up by default. To produce meaningful Mash-Up and Crunch output, enable at least one oscillator by setting its weight > 0.

Relative weights: RSI at 2 and Stochastic at 1 makes RSI twice as influential in the Mash-Up as Stochastic.

Maximum 2.

Plot [Oscillator] TF1 / TF2 / TF3 / TF4 Default: Off (all)

Four individual plot toggles — one per TF — for this oscillator. Enable whichever you want to see. Plotting and Mash-Up contribution are independent: an oscillator can be plotted without contributing to the Mash-Up (Weight = 0), or can contribute to the Mash-Up without being plotted.

Plot [Oscillator] Composite Default: Off

Plots the MTF Composite for this oscillator — a TF-weighted average of TF1-TF4 values using the TF weights from the timeframe settings.

Source Override Default: Off

When on, this oscillator uses its own source (selected in the inline dropdown) instead of the Global Source.

Useful when you want one oscillator on a different price input while others follow the Global Source.

Length Override (per-oscillator-per-TF) Default: Off

When on, per-TF length fields appear for this oscillator, letting you set each TF’s length independently rather than inheriting from that TF’s Default Length.

Oscillator-specific notes: CRSI has two separate length overrides (RSI length and UpDown length). Stochastic has one (K length). Stoch RSI has two (RSI and Stoch lengths). RSI has separate overrides for the RSI period and the MA overlay period.

RSI-specific additional settings:

Plot RSI MA (TF1-TF4 + Composite) Default: Off (all)

Toggles for plotting the moving-average overlay on the RSI line. Independent toggles per TF plus a composite toggle. The MA is computed on the RSI series at each TF.

RSI MA Type Default: SMA

Algorithm for the RSI MA overlay. Options: SMA, EMA, RMA (Wilder’s smoothed MA), WMA, VWMA. One type applies to all TFs simultaneously.

Stochastic-specific additional settings:

Plot Stochastic %D (TF1-TF4 + Composite) Default: Off (all)

Toggles for the %D signal line. Independent per TF plus composite.

%K Smoothing / %D Smoothing Default: 3 / 3

SMA smoothing periods for %K and %D respectively. One value per setting applies across all TFs.

Stoch RSI-specific additional settings:

Plot Stoch RSI %D (TF1-TF4 + Composite) Default: Off (all)

Toggles for the Stoch RSI %D signal line. Independent per TF plus composite.

%K Smoothing / %D Smoothing Default: 3 / 3

SMA smoothing for Stoch RSI %K and %D. Applies across all TFs.

Mash-Up

Plot Mash-Up of TF1/TF2/TF3/TF4 Indicators & Smooth by Default: Off (all), Smoothing = 1

Four toggle-plus-smoothing pairs, one per TF. Each toggle plots the Mash-Up for that TF; the inline number controls SMA smoothing applied to that Mash-Up before plotting.

Mash-Up for a TF requires at least one oscillator to have non-zero weight — otherwise the formula’s denominator is zero and the plot is undefined.

Smoothing = 1 means no smoothing (raw Mash-Up). Larger values smooth the Mash-Up line at the cost of lag. Apply different smoothing per TF if you want shorter TFs to be less noisy than longer TFs.

Crunch

Crunch & Plot All Mash-Ups & Smooth by Default: Off, Smoothing = 1

Toggle for the Crunch line plus SMA smoothing applied after the Crunch formula.

The Crunch is a TF-weighted average of the four Mash-Ups (using TF weights from the TF settings groups). Smoothing = 1 plots the raw Crunch value; larger values smooth it.

Requires at least one oscillator with non-zero Weight in Mash-Up, and at least one TF with non-zero TF weight.

Auto TimeFrame (TF2/TF3/TF4)

13 rows — one per recognized chart timeframe (5m through 3D) — each with three dropdowns: TF2, TF3, TF4 assignment for that chart period. Each dropdown offers a constrained set of valid options for the corresponding TF slot.

TF1 = Xm/XH/XD ? TF2: / TF3: / TF4: Default: See Section 4 for the full default table

For each recognized chart timeframe, three dropdowns configure what TF2, TF3, and TF4 resolve to when Auto-TF is active for that TF.

Changing these allows the auto-TF mappings to be fully customized per chart period. For example, change ‘TF1 = 1H ? TF2’ from 2H to 4H if you prefer a more spaced-out multi-TF view on 1H charts.

Only active for TFs where the “Disable Auto-TF” override is off.

7. Practical Workflow

Minimum Useful Configuration

The absolute minimum to get meaningful output from Oracle:

Set at least one oscillator’s Weight to a non-zero value (e.g., set RSI Weight to 1).
Enable Plot Crunch in the Crunch group.
That’s it. The Crunch now plots using RSI at all four TFs. The oscillator consensus across all timeframes is visible in one line.

From here, expand incrementally: add more oscillators with non-zero weights to enrich the Mash-Up; enable Mash-Up plots to see the per-TF breakdown; enable individual oscillator plots to see what’s driving the composites.

Workflow A — Crunch-Only

Use Oracle’s single most synthesized output as a pure trend filter or momentum gauge.

Set all oscillator weights you want included (e.g., RSI=1, Stoch=1, StochRSI=1).
Enable Plot Crunch.
Apply SMA smoothing to the Crunch (try 3-5) to reduce noise.
Read the Crunch as: above 80 = broad multi-TF overbought; below 20 = broad multi-TF oversold; above 50 trending bullish; below 50 trending bearish.
Don’t look at any other Oracle plot. One line, maximum synthesis.

Workflow B — TF Breakdown

Use the four Mash-Ups to compare timeframe consensus across the TF stack.

Set oscillator weights (same as Workflow A).
Enable all four Mash-Up plots.
Read them together: TF1 Mash-Up is the fastest, TF4 is the slowest. When TF4 is still at 40 but TF1 and TF2 are at 70, the higher timeframes haven’t caught up — cautious reading for bulls. When all four are above 70, all timeframes agree — stronger conviction.
Apply different smoothing per TF: more smoothing on TF1 (noisier) and less on TF4 (already slower). Try Smooth_TF1=3, Smooth_TF2=2, Smooth_TF3=1, Smooth_TF4=1.

Workflow C — Per-Oscillator MTF Views

Use the MTF Composite for a specific oscillator to see how that oscillator reads across all TFs.

Enable Plot [Oscillator] Composite for one oscillator. Leave the others off.
The composite line reflects that oscillator’s cross-TF average. Compare it to the individual TF lines (enable them) to see where the disagreement is.
Useful when you trust one specific oscillator more than others and want it read across all timeframes simultaneously.

Using Oscillator Weights for Conviction

Oscillator weights are a powerful tuning lever. Practical patterns:

RSI=2, Stoch=1 — RSI dominates the Mash-Up; Stoch provides directional tiebreaking.
RSI=1, Stoch=1, StochRSI=1 — equal weighting of three; CMO and CRSI at 0 keep the Mash-Up from being diluted by their more volatile readings.
All at 1 — completely equal contribution; the Mash-Up reflects pure average.
CMO=2, all others=0 — Mash-Up IS CMO. Use when you only want CMO but want it across all four TFs in the Crunch.

Combining With Other Indicators

Oracle synthesizes momentum state across timeframes. It doesn’t generate signals, identify price levels, or track aggression. Practical use combines Oracle with:

Price-based indicators for directional entry (Strata’s MAs, Fluctus’s ZigZag/divergence) for timing.
Order-flow indicators (Balena, CVD Pro, Volumentum) for participation confirmation.
Level-based indicators (Dominium) for the structural picture Oracle’s Crunch should be read against.

8. Troubleshooting and FAQ

No plots appear

Every plot defaults to off. Open settings and toggle on what you want. For Mash-Up and Crunch specifically, also check that at least one oscillator has a non-zero Weight — without that, the formula denominator is zero and the output is undefined.

Crunch shows a flat line at an unexpected value

Every oscillator has Weight = 0 by default. If you enable Plot Crunch without setting any oscillator weight, the Crunch formula divides by zero and PineScript returns na, which may show as a flat line at a specific value depending on the chart’s rendering. Set at least one oscillator’s Weight > 0.

The auto-TF isn’t picking up my chart’s timeframe

Oracle’s auto-TF recognizes 12 specific timeframes: 5m, 15m, 30m, 1H, 2H, 3H, 4H, 6H, 12H, 1D, 2D, 3D. Unrecognized timeframes (10m, 45m, 1W, 1M, Renko, etc.) fall back to the manual TF setting. Enable the Override toggle for TF2/TF3/TF4 and set them manually.

Higher TF plots step rather than flowing smoothly

Expected. Higher-timeframe oscillators computed via request.security update only when those TF’s bars close. On a 5m chart, TF4 at 4H only updates every 48 bars — the 4H TF’s oscillator holds its last value until the 4H bar closes, producing a step-function appearance on the 5m chart. This is correct MTF behavior.

Confirmed mode shows nothing on the current bar

Expected. Confirmed bar-state means the live (unconfirmed) bar doesn’t plot. The chart shows only the last confirmed bar’s values. The current bar plots once it closes. Use Real Time mode to see live bar values.

Mash-Up at 50 but I expected higher

The Mash-Up’s value depends on which oscillators are weighted in. An oscillator weighted at 0 doesn’t contribute. Check which oscillators have non-zero weights — if only one oscillator is active, the Mash-Up equals that oscillator’s value, not some broader consensus.

Individual oscillator lines look different from what I expect

Check the length settings. All oscillators default to the TF’s Default Length (12). If you expected RSI at length 14, either change the Default Length to 14 or enable the Length Override for RSI and set it to 14 manually.

9. Limitations and Design Notes

What Oracle Does Not Do

It does not generate buy or sell signals. The Crunch and Mash-Ups are momentum and consensus reads; trade decisions are the trader’s interpretation.
It does not include MFI or ADX. Unlike its sibling Omnia, Oracle doesn’t include volume-based or trend-strength oscillators. It focuses on price-momentum oscillators that share the 0-100 scale natively or after rescaling.
It does not adapt weights dynamically. Oscillator and TF weights are fixed user settings. There’s no algorithm that learns which oscillators or timeframes to weight more in different market conditions.

The Aggregation Hierarchy Is Fixed

Oracle always aggregates in this order: oscillators → Mash-Up → (across TFs) → Crunch. The user controls the weights at each step, but can’t reorder the aggregation. The Crunch is always built from Mash-Ups; Mash-Ups are always built from individual oscillators. This is deliberate — the hierarchy has a clear interpretation at each level.

All Oscillator Weights Default to Zero

Unlike Omnia which ships Stochastic and Stoch RSI with Weight = 1, Oracle defaults every oscillator weight to 0. With all weights at 0, the Mash-Up and Crunch formulas divide by zero and produce no output. The user must explicitly activate oscillators for the composites to work.

This is deliberate. Oracle is a more advanced tool than Omnia — its users are expected to configure it consciously rather than rely on defaults. The opt-in-everything philosophy prevents the indicator from producing output that the user didn’t intentionally design.

Relationship to Omnia

Oracle and Omnia share the same five oscillators (CMO, CRSI, RSI, Stochastic, Stoch RSI) and the same Mash-Up concept, but Oracle extends in two important directions: full multi-timeframe computation via request.security for all oscillators, and the Crunch as a second-level aggregation across timeframes.

Omnia is simpler and more immediately accessible. Oracle requires more configuration investment but produces a more comprehensive picture. The choice between them: use Omnia for single-TF multi-oscillator analysis; use Oracle when multi-timeframe consensus is the goal.

Computational Load

Oracle makes many request.security calls — one per oscillator per higher TF, for each enabled plot. With four TFs and five oscillators, that’s up to 15 request.security calls. PineScript allows a large but finite number per script. Oracle stays within limits when all features are used simultaneously, but adding external indicators with many request.security calls to the same chart may hit the limit. If charts become slow or error, disable unused oscillator TF plots to reduce the load.

Crunch as the Terminal Insight

The Crunch is the most information-dense single output Oracle can produce — a simultaneous account of five oscillators across four timeframes, distilled into one 0-100 number. Its value isn’t in the absolute number alone (oscillators can be structurally biased high or low depending on market regime) but in its direction, velocity, and location relative to the reference levels. The Crunch crossing 50, reaching 80, or diverging from the Mash-Up on TF4 while TF1 agrees — these are the reads. The raw number is a starting point, not the conclusion.

Closing Note

Oracle does one thing that most oscillator indicators can’t: it simultaneously asks “what does the consensus of five oscillators say about this price, at each of four timeframes, and what does the consensus of those four timeframe-specific readings say overall?” The Crunch is the answer. Its value depends entirely on the weights the trader assigns — different weight configurations create meaningfully different indicators within the same shell. The manual describes the mechanics; the configuration is the trader’s analytical expression.