Skip to content

KB/signal

CTA SMA 50

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.

CTA SMA 50

What it is

CTA SMA 50 — registry key cta_sma_50.

50-day simple moving average of SPY close. One of the most-watched CTA trigger levels — systematic funds flip net-long when SPY crosses above. Captured alongside sma_20/sma_100/sma_200 from market.py:_analyze_cta_proxy; previously computed then discarded.

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: market
Data source: back_fillable

Fetched directly from app/sources/market.py; see source code for the upstream API call and any provider-specific handling.

How it’s computed

50-day simple moving average of SPY close, computed in market.py:_analyze_cta_proxy from the same 1-year market-data fallback/brokerage data session history fetch used by the CTA stack-score. Extracted via engine.py _build_sig_input from data[‘cta_proxy’][‘sma_50’].

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