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.

Oil Price Spike

Alert ID: OIL_SPIKE
Category: geopolitical
Cross-detection: no

Severity

WARNING — conditions deteriorating; worth monitoring

Trigger condition

{
  "type": "or",
  "conditions": [
    {
      "field": "uso_close",
      "op": "gt",
      "value": 75
    },
    {
      "type": "computed",
      "computation": "uso_day_spike"
    }
  ]
}

Any of the following must hold:

• uso_close > 75
• Computed condition (uso_day_spike) — 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

Oil spike alert: USO at ${uso_close} — potential geopolitical disruption or supply shock.

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.

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

• Signal fields referenced: uso_close (no dedicated KB article yet — see /humans#signal-reference).
• Alert reference (legacy monolith)
• Live alerts feed