Incidents

Deployment-scoped incidents with a five-state, forward-only lifecycle and an audited timeline. Nothing here is inferred — an incident exists because an operator declared it. Signal correlation and on-call routing are a follow-up.

Incidents

SEVERITY

STATE

SCOPE

0 rows

Declared incidents, newest first
			Owner
No incident has been declared Nothing has been declared on this deployment. An incident exists because an operator declared it — it is never inferred — so an empty tracker is the good state, not a failed read.