KB / alert
Financial Conditions vs Score Divergence
Last verified
Auto-generated. This article is rebuilt from
app/signals/config/alert_thresholds.jsonbyscripts/build_alerts_kb.py. Edit the alert config and re-run the script — do not edit this file directly.
Financial Conditions vs Score Divergence
Alert ID: NFCI_SCORE_DISAGREE
Category: composite
Cross-detection: no
Severity
WARNING — conditions deteriorating; worth monitoring
Trigger condition
{
"type": "and",
"conditions": [
{
"field": "nfci",
"op": "gt",
"value": 0
},
{
"field": "health_score",
"op": "gt",
"value": 60
}
]
}
All of the following must hold:
nfci> 0health_score> 60
Message template
Divergence: NFCI at {nfci:.3f} (tight) while health score reads {health_score:.0f} — financial conditions may be a leading headwind.
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(oracknowledged) row peralert_idat a time. Re-firing while active updatesfired_atand the message but keeps the originalfirst_fired_at.
Notifies
- Active alert feed (
/api/v1/alerts/active,/alerts/summary). - SSE stream (
/api/v1/agents/stream) for real-time consumers. alert_firedwebhook on first fire.alert_resolvedwebhook when the condition clears (non-cross-detection alerts only).