Sigma Deviation as Normalized Signal

Module 06 · Lesson 6.1

σ Deviation as Normalized Signal

Raw numbers lie about magnitude. A move of 100 means one thing in NVDA and something completely different in gold. Standard deviations turn raw metrics into a unitless, comparable scale that lets the framework treat signals from different tickers, asset classes, and time horizons in the same language.

Reading13 minDifficultyIntermediatePrereqsLesson 1.1

6.1.1Why Normalize at All

The single most pervasive analytical mistake in trading is comparing raw numbers across instruments without normalization. A ten-point move in SPY (currently $723.71) is roughly 1.4%. A ten-point move in NVDA is closer to 5%. A ten-point move in gold is about 0.4%. The same headline number maps to wildly different magnitudes of significance depending on the instrument’s natural scale and natural volatility. Sizing decisions made on raw numbers will be systematically wrong — oversized in low-vol names, undersized in high-vol names, and impossible to compare across.

Standard deviations solve this. A move of +1σ means the same thing in every instrument: one historical standard deviation away from the mean of the relevant baseline. The unit is not dollars, percent, or shares; it is “how unusual is this move relative to its own recent history.” That makes signals across instruments commensurable, which is the precondition for any cross-sectional ranking, any composite score, and any sizing framework that wants to treat opportunities as belonging to the same risk space.

The intuition map is direct. Roughly 68% of moves fall within +/-1σ of the mean, 95% within +/-2σ, and 99.7% within +/-3σ under a normal distribution. A +2σ move is in the 97.5th percentile of moves; a +3σ move is in the 99.85th percentile. When the framework flags a +2.4σ flow event, it is saying “this print is in the top 1% of similar prints over the relevant window.” That is information-dense in a way the raw print rarely is.

Raw numbers are vocabulary. Sigma is grammar. The grammar is what lets you compare anything to anything across the framework.

6.1.2Computing σ on Rolling Baselines

The standard deviation calculation requires a baseline (the mean) and a dispersion estimate (the standard deviation around the mean). Both should be computed on rolling windows, not on all-time history, because the right baseline for “is today unusual?” is the recent past, not the inception of the instrument. The AZTMM default is a 90-day rolling window for most signals, with shorter windows (30-day) for vol-sensitive signals and longer windows (250-day) for regime signals.

The mechanic is direct. For each day, compute the mean of the prior 90 days of the metric, compute the standard deviation of those same 90 days, and report today’s value as (today – mean) / stdev. The output is the σ deviation. A σ reading of +1.22 means today is 1.22 standard deviations above the 90-day mean. A reading of -2.1 means today is 2.1 standard deviations below the mean — a meaningfully negative outlier.

The rolling window adapts naturally to regime change. When realized volatility rises, the standard deviation in the denominator rises, and the σ reading on a given raw move falls — correctly noting that what looked like a +2σ move in a quiet regime is only a +1σ move in a volatile regime. When realized volatility falls, the same raw move becomes a higher σ reading. The framework adapts to the environment without requiring manual recalibration.

6.1.3Reading σ on Flow Data

The clearest application is options flow. Today’s call/put dollar ratio of 2.19× sounds high, but the question is whether it is high relative to the recent baseline. The 90-day mean of call/put ratios is 1.42×, with a standard deviation of 0.63. Today’s reading is therefore (2.19 – 1.42) / 0.63 = +1.22σ. That is meaningful but not extraordinary — in the top quintile of recent days but not in the top decile.

The interpretation depends on the regime. In a Bull regime, a +1.22σ call/put reading is consistent with the regime — bullish positioning is what the regime predicts — and is corroborating rather than informational. In a Crisis regime, the same +1.22σ call/put reading would be a meaningful divergence from the regime, suggesting either contrarian positioning or a leading indicator of regime transition. The same number reads differently because the baseline expectation has shifted.

The same logic applies to dark pool prints, gamma exposure, breadth indicators, and any other metric the framework tracks. The σ reading is not the answer; it is the input that makes the metric comparable across days, tickers, and regimes.

MetricToday90d Mean90d StDevσ Reading
SPY call/put dollar ratio2.19×1.42×0.63+1.22σ
SPY notional flow ($M)4,8203,410720+1.96σ
SPY breadth (% >50DMA)62%58%9%+0.44σ
VIX close14.115.82.4-0.71σ
HYG/LQD ratio0.8020.7950.018+0.39σ
Learning Check
NVDA’s daily flow notional is $1.8B today. The 90-day mean is $900M with a standard deviation of $240M. SPY’s daily flow is $4.8B with a 90-day mean of $3.4B and standard deviation of $720M. Which print is more unusual?
NVDA is meaningfully more unusual. NVDA’s reading is (1800-900)/240 = +3.75σ, which is a 99.99th-percentile day. SPY’s reading is (4820-3410)/720 = +1.96σ, which is around the 97.5th percentile. The raw NVDA notional ($1.8B) is less than half of SPY’s ($4.8B), so reading the raw numbers would suggest SPY is the bigger story. The σ normalization correctly identifies that NVDA is having a top-1-in-10000-days flow event while SPY is having a top-1-in-40-days event. The framework should weight NVDA’s signal far more heavily, exactly the opposite of what raw notionals would suggest.

6.1.4Comparing Across Tickers and Asset Classes

The cross-sectional ranking use of σ is the workhorse application. The Daily Pulse and Weekly Pulse both rank tickers by signal strength using σ as the unifying metric. NVDA flow at +3.75σ ranks above SPY flow at +1.96σ, regardless of the dollar amounts. The reader does not have to remember the natural notional level of each ticker; the σ column does that work.

The same is true across asset classes. A +2.1σ move in 10Y yields, a +1.4σ move in DXY, and a +2.6σ move in HYG/LQD can all be displayed in the same multi-asset table and compared at a glance. Without normalization, the table would be unreadable; the natural units of yields (basis points), DXY (index points), and HYG/LQD (ratio decimals) are not commensurable. With σ normalization, the table becomes a single coherent ranking.

The cross-sectional discipline extends to portfolio construction. When ranking the day’s setups, the σ readings on each input (flow, dark pool, technicals, regime) can be summed or weighted into a composite score that is comparable across instruments. A composite of +5σ aggregated across four inputs on TSLA is a more compelling setup than a +3σ aggregate on AMD, regardless of the underlying tickers’ natural volatilities.

6.1.5Failure Modes & Fat Tails

The σ framework assumes a roughly normal distribution of the underlying metric. Markets are not normally distributed. They have fat tails — extreme events occur far more frequently than the normal distribution would predict. A 6σ event in equities under a normal distribution should occur roughly once every several billion trading days; in actual market history, 6σ events occur multiple times per decade. The model is wrong about the tail.

The implication is that σ is reliable for the body of the distribution (everything within +/-2.5σ) and unreliable for the extremes (beyond +/-3σ). For tail events, the better measure is percentile — “what fraction of the prior 250 days were as extreme as this?” For body events, σ is more useful because it preserves continuity and allows arithmetic. The discipline is to know which regime you are in: if a metric reads +4σ or worse, switch to percentile reasoning before sizing or interpreting.

Other failure modes are more subtle. σ assumes the variance is stable over the rolling window; if the variance itself is shifting (the regime is changing volatility), the σ reading lags and either understates the move (when vol is rising) or overstates it (when vol is falling). The fix is to overlay the σ reading with a separate vol-of-vol check: if realized vol over the last 10 days is meaningfully different from the 90-day baseline, treat all σ readings on the metric with caution.

ReadingTrust σ or Percentile?Why
+/- 0 to 1σσ (continuous, comparable)body of distribution
+/- 1 to 2.5σσ (still calibrated)upper body, mostly normal
+/- 2.5 to 3.5σσ with cautionedge of trustable normality
+/- 3.5 to 5σpercentile preferredfat tail begins
beyond +/- 5σpercentile onlytail event, σ meaningless
Learning Check
A flow signal reads +5.6σ on a single name. The 90-day stdev for that signal is unusually small because the prior 90 days were quiet. How should you interpret the print?
The σ reading is unreliable for two reasons: it is in the fat-tail region where the assumption of normality breaks down, and the denominator (the 90-day stdev) is artificially compressed by a quiet baseline period, which inflates the σ reading. The correct read is to switch to percentile: was today’s raw value above the 99th percentile of the prior 250 days? If yes, the signal is genuinely extreme and worth attention. If no, the +5.6σ reading is a math artifact of a quiet baseline and the signal is meaningfully smaller than the σ suggests. Always cross-check fat-tail readings against percentile, never size based on a σ alone above 4.

6.1.6Common Mistakes

  • Comparing raw numbers across tickers. A 10-point move in NVDA is not commensurable with a 10-point move in SPY.
  • Reading σ without checking the baseline window. A 30-day σ and a 250-day σ on the same metric tell different stories.
  • Trusting fat-tail σ readings. Beyond +/-3.5σ, switch to percentile.
  • Ignoring vol-of-vol shifts. A σ reading is unreliable when the variance itself is changing.
  • Treating the same σ the same across regimes. +1.22σ bullish flow reads differently in Bull vs Crisis regime.
  • Aggregating σ readings without correlation adjustment. Summing four correlated +1σ signals is not a +4σ composite.

Key Takeaways

  • σ turns raw metrics into a unitless, comparable scale across tickers, asset classes, and time horizons.
  • Compute against a rolling baseline (90-day default; 30 for vol, 250 for regime).
  • +/-1σ covers 68% of moves, +/-2σ covers 95%, +/-3σ covers 99.7% (under normality).
  • Beyond +/-3.5σ switch to percentile because fat tails make the framework break down.
  • Cross-sectional ranking by σ is the workhorse for daily and weekly pulse outputs.
  • The same σ reads differently across regimes; always interpret σ against the prevailing regime expectation.

Subscribe to AZTMM IDE

Daily Pulse and Weekly Pulse to your inbox, end-of-session. Observations, not advice. Unsubscribe any time.

We don’t spam! Read our privacy policy for more info.