Skip to content

KB/signal

NFCI 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.

NFCI signal

What it is

NFCI signal β€” registry key nfci_signal.

Computed NFCI classification label (Loose/Normal/Tight).

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: macro_indicators
Data source: computed

Derived metric β€” produced inside the platform (app/sources/macro_indicators.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 nfci classifier β€” Loose / Neutral / Tight / Crisis β€” per signal_defs.band_for('nfci', value). Weekly Chicago Fed financial-conditions index sign + magnitude.

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-7): band label over nfci β€” mirrors parent nfci’s weekly Wednesday/lag-7 calendar; was mislabeled intraday.

See also