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.

Squeeze setup state

What it is

Squeeze setup state — registry key squeeze_setup_state.

Companion column to squeeze_setup_score; carries the state label / active-trigger list (see app/signals/squeeze.py).

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

Categorical state from squeeze_setup_score: ‘primed’ (≥3 triggers) / ‘partial’ (2 triggers) / ‘none’ (0–1 triggers). See app/signals/squeeze.py:PRIMED_THRESHOLD.

Where it surfaces

• API field: positioning.squeeze_setup.state on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)

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.