<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident Review on Fondsites</title><link>https://fondsites.com/tags/incident-review/</link><description>Recent content in Incident Review on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 13:43:57 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/incident-review/feed.xml" rel="self" type="application/rss+xml"/><item><title>Robot Incident Review and Near Misses: Learning Before The Next Collision</title><link>https://fondsites.com/physical-ai-lab/guidebooks/robot-incident-review-near-misses/</link><pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/physical-ai-lab/guidebooks/robot-incident-review-near-misses/</guid><description>&lt;p&gt;A robot incident is rarely a single moment.&lt;/p&gt;
&lt;p&gt;The visible part may be a stopped mobile base, a dropped tote, a pinched cable, a blocked aisle, an emergency stop, a collision with a cart, or a human who stepped back faster than expected. The useful story usually starts earlier. A map changed. A route became crowded. A sensor slowly lost clarity. A maintenance check slipped. A software update changed speed behavior. An operator learned that the fastest way to keep production moving was to restart the robot without writing down why it stopped.&lt;/p&gt;</description></item></channel></rss>