Skip to content

KB/signal

SPY/DXY correlation

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/DXY correlation

What it is

SPY/DXY correlation β€” registry key corr_spy_dxy.

20-day rolling correlation; per-pair classification thresholds live in app/signals/correlations.py:PAIR_CONFIG (not band-reducible). Tracked in history; classification surfaces via the correlations composite component.

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: correlations
Data source: computed

Derived metric β€” produced inside the platform (app/signals/correlations.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

20-day rolling Pearson correlation of daily SPY returns vs daily DXY returns. From daily_signals.spy_close / dxy_close. See app/signals/correlations.py pair spy_dxy.

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

See also