Skip to content

KB/signal

BBB Spread Ξ”20d

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.

BBB Spread Ξ”20d

What it is

BBB Spread Ξ”20d β€” registry key bbb_spread_20d_chg.

20-trading-day change of the BBB credit spread (percentage points), computed at capture time from trailing daily_signals.bbb_spread history. Pure data carrier for the analogue matcher’s drawdown-risk lane β€” no bands, no health-score contribution. The raw bbb_spread level stays display_only (subsumed by hy_oas); only its direction-of-change is the matcher dimension.

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

Change of the BBB credit spread over the last 20 trading rows: bbb_spread(t) - bbb_spread(t - 20 rows), in percentage points. Computed at capture time in app/signals/capture.py:_inject_bbb_spread_20d_chg from the trailing daily_signals.bbb_spread history (the value 20 rows back); NULL when fewer than 20 prior rows carry a bbb_spread. Series exists 2023+ only (zero 2022-bear coverage) β€” historical rows before that stay NULL and the matcher skips the dim for those analogues. Backfilled by scripts/backfill_bbb_spread_chg.py.

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

See also