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/TNX corr signal

What it is

SPY/TNX corr signal — registry key corr_spy_tnx_signal.

Computed classification label string surfaced in the report; underlying numeric metric carries the band semantics. Tracked for marker-flip detection between report cycles.

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

Four-level classification of corr_spy_tnx per correlation_scoring.json pair spy_tnx.

Where it surfaces

• API field: signals.corr_spy_tnx_signal on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)
• Surface: change markers in the rendered report

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

• Publishes: intraday

See also

• /kb/api/get-signals-latest — API endpoint that serves this field.