<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operational Design Domain on Fondsites</title><link>https://fondsites.com/tags/operational-design-domain/</link><description>Recent content in Operational Design Domain 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/operational-design-domain/feed.xml" rel="self" type="application/rss+xml"/><item><title>Robot Operational Design Domains: Drawing Useful Boundaries</title><link>https://fondsites.com/physical-ai-lab/guidebooks/robot-operational-design-domain/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/physical-ai-lab/guidebooks/robot-operational-design-domain/</guid><description>&lt;p&gt;A useful robot does not need to work everywhere. It needs to know where its promises stop.&lt;/p&gt;
&lt;p&gt;That boundary is easy to ignore when a demo works. A mobile robot moves through a clean aisle. A robot arm picks from a prepared tray. A home robot avoids the obvious obstacle. A humanoid carries a tote across a staged room. The moment can be real and still leave out the question that matters most for deployment: under which conditions is the robot actually allowed to act?&lt;/p&gt;</description></item></channel></rss>