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.

Regime Change Detected

Alert ID: REGIME_CHANGE
Category: regime
Cross-detection: yes

Severity

WARNING — conditions deteriorating; worth monitoring

Trigger condition

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

Computed condition (regime_changed) — 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.

Cross-detection alerts fire only on the transition into the trigger state — the condition must have been false on the previous evaluation. Persistent states do not re-fire.

Message template

Regime shifted from {prev_regime} to {regime}.

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

• Cooldown: none. Re-evaluation on every cycle.
• Dedup: at most one active (or acknowledged) row per alert_id at a time. Re-firing while active updates fired_at and the message but keeps the original first_fired_at.
• Cross-detection: does not auto-resolve when the condition clears — the alert row stays as the historical record of the transition itself.

Notifies

• Active alert feed (/api/v1/alerts/active, /alerts/summary).
• SSE stream (/api/v1/agents/stream) for real-time consumers.
• alert_fired webhook on first fire.
• alert_resolved webhook when the condition clears (non-cross-detection alerts only).

See also

• No simple field references — see app/signals/alerts.py:_eval_computed for the computed-condition logic.
• Alert reference (legacy monolith)
• Live alerts feed