Skip to content

KB/signal

SPY distance to ZGL (%)

Last verified

Auto-generated. This article is rebuilt from app/signals/config/signal_definitions.json by scripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.

SPY distance to ZGL (%)

What it is

SPY distance to ZGL (%) — registry key spy_dist_to_zgl_pct.

Signed per-cycle distance between SPY and the zero-gamma level, persisted to intraday_signals only (the daily gamma-flip read lives in the gamma_flip/pct_to_flip family). Registered 2026-06-12 (coherence audit PR-5 / L1-13) — column existed since P12 (2026-04) with no registry entry.

Data-pyramid tier

T1 — Signal. This metric sits at the signal layer of the platform’s six-tier data pyramid (T0 raw inputs → T5 actionable read). The tier reflects how far the value is from a raw measurement — not how strongly it is validated. Abstraction and validation are separate axes: a higher tier is not a claim of stronger evidence.

Horizon & validation

No validated skill horizon is on file for this metric — read it as context / a data carrier, not a validated edge. Stamps are added only when a gated research verdict lands.

Source

Source module: capture
Data source: computed

Derived metric — produced inside the platform (app/signals/capture.py or equivalent) rather than fetched as a raw upstream value. See the How it's computed section below for the formula.

How it’s computed

spy_dist_to_zgl_pct = (spy_close - spy_zgl) / spy_close * 100, rounded to 3 decimals; NULL when either input is missing. Signed: positive = SPY above the zero-gamma level (vol-dampened tape), negative = below (vol-amplified, trending tape). Computed in app/signals/capture.py:_upsert_intraday; served in /api/v1/signals/intraday-replay bars.

Where it surfaces

Health-score / alignment role

Data carrier — no implication, no health-score contribution.

Persisted for downstream consumers (sparklines, base-rate matcher, calibration substrate) but does not classify into BULLISH / NEUTRAL / BEARISH and does not contribute to the 0-100 health score.

Release cadence

Computed every capture cycle from spy_close + spy_zgl (live chain ZGL).

See also