KB / signal
A5 mechanical-selling reversion triggers
Last verified
Auto-generated. This article is rebuilt from
app/signals/config/signal_definitions.jsonbyscripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.
A5 mechanical-selling reversion triggers
What it is
A5 mechanical-selling reversion triggers — registry key a5_mechanical_triggers.
Human-readable list of fired conditions from the A5 scorer. E.g. [‘rebalance_window: sp500_rebalance_q4’, ‘beta_residual -3.2pp’, ‘quality:pass’]. 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_mechanical_reversion. See app/screener/archetypes.py.
Where it surfaces
- API field:
screener.candidates.a5.triggersonGET /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