<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spoiledlunch</title><link>https://23d5796d.spoiledlunch.pages.dev/</link><description>Nerdy Stuff. Tech Talk. Zero Freshness. Analysis and commentary on GRC, security, and AI.</description><generator>Hugo 0.160.1</generator><language>en-us</language><lastBuildDate>Tue, 23 Jun 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://23d5796d.spoiledlunch.pages.dev/tags/ai-incident-response/" rel="self" type="application/rss+xml"/><item><title>Why AI Incident Response Is Still Underbuilt Almost Everywhere</title><link>https://23d5796d.spoiledlunch.pages.dev/articles/2026-05-01-why-ai-incident-response-is-still-underbuilt-almost-everywhere/</link><pubDate>Tue, 23 Jun 2026 09:00:00 -0400</pubDate><guid>https://23d5796d.spoiledlunch.pages.dev/articles/2026-05-01-why-ai-incident-response-is-still-underbuilt-almost-everywhere/</guid><description>Article • June 23, 2026 • 4 min read | Topics: AI | Most organizations now have some language about responsible AI.
Far fewer have a credible answer to a simpler question: what happens when an AI system causes a production problem on a Tuesday …</description><author>Spoiledlunch</author><category>AI</category><category>ai incident response</category><category>ai governance</category><category>operations</category><category>monitoring</category></item></channel></rss>