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.

Gap (open vs prev close)

What it is

Gap (open vs prev close) — registry key screener_gap.

Per-ticker open-gap: (today_open - prev_close) / prev_close. Stored in screener_features_daily; not a health-score or alignment component. Feeds archetype scorers (A1 post-earnings overreaction, D4 gap-fill magnet).

Source

Source module: screener
Data source: computed

Derived metric — produced inside the platform (app/sources/screener.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

(today_open - prev_close) / prev_close. NULL when open price is unavailable or fewer than 2 rows of history exist.

Where it surfaces

• API field: screener.features.gap on GET /api/v1/signals/latest

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