<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Change Control on Fondsites</title><link>https://fondsites.com/tags/change-control/</link><description>Recent content in Change Control 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/change-control/feed.xml" rel="self" type="application/rss+xml"/><item><title>Robot Software Updates and Change Control: Keeping Autonomy Stable</title><link>https://fondsites.com/physical-ai-lab/guidebooks/robot-software-update-change-control/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/physical-ai-lab/guidebooks/robot-software-update-change-control/</guid><description>&lt;p&gt;A robot software update is never just a software update.&lt;/p&gt;
&lt;p&gt;It changes a machine that moves through space, carries loads, senses people, follows maps, obeys safety limits, asks operators for help, and leaves evidence when something goes wrong. A small code change can alter stopping behavior, route choice, grasp timing, battery use, network dependence, alert wording, or the way a robot recovers after confusion. In ordinary software, a bug may frustrate a user. In robotics, the same habit can block an aisle, drop a part, damage a fixture, or teach workers that the machine cannot be trusted.&lt;/p&gt;</description></item></channel></rss>