<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident Response on Fondsites</title><link>https://fondsites.com/tags/incident-response/</link><description>Recent content in Incident Response on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 12 May 2026 02:06:09 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/incident-response/feed.xml" rel="self" type="application/rss+xml"/><item><title>AI Agent Incident Response: What to Do When Delegation Goes Wrong</title><link>https://fondsites.com/ai-agents/guidebooks/agent-incident-response/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/ai-agents/guidebooks/agent-incident-response/</guid><description>&lt;p&gt;AI agent incidents do not always look like disasters. Sometimes they look like a support draft sent to the wrong customer segment, a file edited more broadly than intended, a workflow stuck in a retry loop, a tool call made with stale context, a database update that should have waited for review, or a series of small mistakes that nobody notices until the queue is messy. Delegation went wrong, but not in a cinematic way.&lt;/p&gt;</description></item></channel></rss>