Incident response

This is a proposed direction, not an available feature or a delivery commitment. No release date is assigned.

Operator problem

Responders need a shared sequence of observed alerts and recovery, with explicit responsibility.

Current alpha boundary

Alert definitions, notification policies and firing/resolved records exist. They do not by themselves implement incident ownership, on-call escalation or a complete response timeline. See the current operator guide.

Proposed capability

Investigate acknowledgement, evidence references and ownership using the existing alert lifecycle.

Evidence required

Prove duplicate notifications, late recovery, delivery failures and reloaded state with a real receiver before claiming coordination.

Non-goals

No paging-network guarantee, automatic remediation or synthetic incident history.

Contribution entry

Bring a concrete workflow and a reproducible failure to the contribution process. Agree the smallest contract and acceptance evidence before implementation. Return to the roadmap.