Skip to content

KB/signal

DIX signal

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.

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.

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

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

cadence corrected 2026-06-12 (PR-4/L1-8): band label over dix — mirrors parent dix’s daily EOD-CSV calendar (prior_close during the live session); was mislabeled intraday.

See also