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.

Alignment severity

What it is

Alignment severity — registry key alignment_severity.

Severity label from compute_alignment (STRONG_ALIGNMENT / MIXED / DIVERGENCE).

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

Categorical label from alignment_score + bullish/bearish count: STRONG_ALIGNMENT (5+ aligned) / MODERATE_DIVERGENCE / STRONG_DIVERGENCE (5+ divergent) / MIXED. See app/signals/regime.py:_classify_severity.

Where it surfaces

• API field: alignment.severity on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)

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-alignment — API endpoint that serves this field.