Skip to content

KB/signal

Breadth (200d)

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.

Breadth (200d)

What it is

Breadth (200d) β€” registry key breadth_200d.

Breadth scoring uses 50d only; 200d provides longer-term context for the composite breadth_signal.

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

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

How it’s computed

Percent of S&P 500 constituents whose latest close is above their own 200-day SMA: count(close > sma200) / count(valid) Γ— 100. See app/sources/breadth.py:84.

Where it surfaces

Bands / thresholds

Classifier direction: higher_is_better.

Range Label Dot Implication Points
β€” Strong trend favorable BULLISH β€”
β€” Moderate trend leaning NEUTRAL β€”
β€” Mixed neutral NEUTRAL β€”
β€” Weak trend cautionary BEARISH β€”

Health-score / alignment role

Display-only β€” has bands for surface labeling but does not contribute to the health score (scoring is handled by a companion metric).

Release cadence

See also