Skip to content

KB/alert

Screener High-Conviction Candidate

Last verified

Auto-generated. This article is rebuilt from app/signals/config/alert_thresholds.json by scripts/build_alerts_kb.py. Edit the alert config and re-run the script β€” do not edit this file directly.

Screener High-Conviction Candidate

Alert ID: SCREENER_HIGH_CONVICTION
Category: screener
Cross-detection: no

A new single-name screener candidate appeared at conviction tier β€˜high’. Fired per-ticker by the screener pipeline (app/signals/screener_alerts.py), NOT by the macro alert engine. Only fires when the candidate’s firing archetype is CALIBRATED (n>=30 matured samples) β€” uncalibrated archetypes never alert. The calibrated hit-rate is labeled in the message (honesty discipline).

Severity

INFO β€” positive signal or notable event; no action needed

Trigger condition

{
  "type": "computed",
  "computation": "screener_high_conviction"
}

Computed condition (screener_high_conviction) β€” the trigger logic lives in app/signals/alerts.py:_eval_computed. This alert does not decompose into a simple field threshold; consult the source for the exact semantics.

Message template

Screener: {ticker} β€” new HIGH-conviction candidate (conviction {conviction}/100, regime {regime_tag}, {calibration_label}). Worth a look.

Rendered with the current signals dict via Python str.format. Placeholders that fail to resolve fall back to the raw template (see _format_message in app/signals/alerts.py).

Cooldown / dedup

Notifies

See also