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 signal

What it is

Breadth signal — registry key breadth_signal.

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

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: computed

Derived metric — produced inside the platform (app/sources/breadth.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

Band label from pct_above_50sma classifier — Healthy (≥60%) / Mixed (40–60%) / Weak (20–40%) / Washout (<20%). See app/sources/breadth.py:122.

Where it surfaces

• API field: signals.breadth_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.