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.

DIX signal

What it is

DIX signal — registry key dix_signal.

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

Source

Source module: darkpool
Data source: back_fillable

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

How it’s computed

Band label from dix_band classifier — Favorable (≥0.48) / Leaning (0.45–0.48) / Neutral (0.42–0.45) / Cautionary (0.40–0.42) / Adverse (<0.40). See app/signals/signal_defs.py:band_for('dix', value).

Where it surfaces

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