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 next-3d return

What it is

SPY next-3d return — registry key spy_next_3d_rtn.

Realized forward return persisted for matcher calibration. Three-trading-day lag.

Data-pyramid tier

T0 — Raw input. This metric sits at the raw input 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

Realized SPY 3-day forward return: (spy_close[T+3] − spy_close[T]) / spy_close[T]. Backfilled when row T+3 lands. Same backfill helper as spy_next_1d_rtn. Used by the base-rates matcher.

Where it surfaces

• API field: signals.spy_next_3d_rtn on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)
• Surface: /signals/history time series

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: daily
• Lag days: 3

Backfilled onto row T when row T+3’s spy_close lands.

See also

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