Skip to content

KB/signal

Curve 2s10s 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.

Curve 2s10s signal

What it is

Curve 2s10s signal — registry key curve_2s10s_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: computed
Data source: computed

Derived metric — produced inside the platform (app/signals/computed.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 curve_2s10s classifier per signal_defs.band_for('curve_2s10s', value) — inverted / flattening / normal / steep.

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-6 extension): band label over curve_2s10s from the same credit.py T-1 FRED fetch — mirrors parent’s daily/lag-1 calendar; was mislabeled intraday.

See also