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.

Cascade stage

What it is

Cascade stage — registry key cascade_stage.

Transmission-cascade tracker diagnostic (see app/signals/cascade.py); state value, not a classifier band.

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

Position on the risk-off cascade ladder — STAGE_0 / STAGE_1 (early warning) / STAGE_2 (broadening) / STAGE_3 (full risk-off) — based on how many of the 4 cascade triggers are firing. See app/signals/cascade.py.

Where it surfaces

• API field: signals.cascade_stage on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)
• Surface: /signals/history time series
• Surface: /signals/sparklines (UI sparklines)

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.