Automated incident checks
Confirms schema v26, strong-auth ownership, deadline/severity guards, escalation idempotency, delivery-job handoff and immutable incident history.
NOT RUNSchema check has not run yet.
NOT RUNSelf-test has not run yet.
v0.12.27 · INCIDENT RESPONSE + DELIVERY RELIABILITY
A high-severity alert should turn into an owned, timed response—not sit in a queue forever.
Incident response now hands notification work into the v0.12.27 leased retry/dead-letter delivery layer. Human incident actions still require strong-auth; real pager/email/on-call providers remain a production gate.
High alert → incident → ownership → escalation
Use this in staging. Opening the incident is allowed before MFA because automated production monitoring will eventually create incidents. Human ownership and state changes require step-up.
READYStart with a QA Incident Admin session.
Incident ownership & response
Before step-up: click Assign to me and expect an orange EXPECTED BLOCK. After enrolling and stepping up, ownership, investigation, containment and resolution should turn green.
No QA Incident Admin dashboard loaded yet.
Escalation delivery queue
The queue now hands each notification to the durable v0.12.27 delivery job layer. Use Delivery Reliability QA for lease, retry, stale-worker and dead-letter testing.
No incident notification jobs loaded yet.
Production incident-response evidence
These stay open until the corresponding production systems actually exist and have been rehearsed.
Recent incident QA runs
No QA runs recorded yet.
Evidence tools
Clearing browser QA evidence does not rewrite server-owned incident, escalation or staff-security records.