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.

Re-entry / oversold score

What it is

Re-entry / oversold score — registry key reentry_score.

Deep-oversold re-entry state flag (2026-06 re-entry/upswing research; long-side mirror of the air-pocket flag). Deterministic STATE descriptor — NOT scored, NOT a predictor; no classification bands, no health-score contribution.

Data-pyramid tier

T3 — Lens. This metric sits at the lens 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

Number of re-entry triggers currently firing (0–4): deep_flush (spy_close <= cta_sma_50 * (1 - 0.05), i.e. price >=5% below the trailing 50-day SMA — the research’s high-probability re-entry zone, NOT the shallow -2..-5% trap) + capitulation_breadth (pct_above_50sma <= 30.0) + fear_spike (vix_close >= 22.0 — buying into peak fear, not the roll-over) + bounce_fuel (squeeze_setup_state in {partial, primed}). See app/signals/reentry.py:evaluate_reentry.

Where it surfaces

• API field: positioning.reentry.score 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.