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.

A3 positioning extreme triggers

What it is

A3 positioning extreme triggers — registry key a3_positioning_triggers.

Human-readable list of fired conditions from the A3 scorer. E.g. [‘short_pct 18.3% (extreme)’, ‘price_holding: ret_20d -0.02’, ‘options leg: pending Phase 3’]. Serialized as JSON array string.

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

List of triggered condition strings assembled in evaluate_positioning_extreme. See app/screener/archetypes.py.

Where it surfaces

• API field: screener.candidates.a3.triggers 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