<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Robotics on AI Tools</title>
    <link>https://ait.bsc.es/industries/robotics/</link>
    <description>Recent content in Robotics on AI Tools</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://ait.bsc.es/industries/robotics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Robot Task Planner</title>
      <link>https://ait.bsc.es/blueprints/robot-task-planner/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/robot-task-planner/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;Translate natural-language instructions into validated, bounded action sequences for a robot.&lt;/p&gt;&#xA;&lt;p&gt;This page shows the structure a blueprint detail page uses. The problem statement and component list below are real design context; the deployment and usage sections are placeholders.&lt;/p&gt;&#xA;&lt;h2 id=&#34;problem-addressed&#34;&gt;Problem addressed&lt;/h2&gt;&#xA;&lt;p&gt;Natural-language robot instruction is appealing, but a model that can emit arbitrary action sequences is a safety problem: the model must propose, and something else must decide.&lt;/p&gt;&#xA;&lt;h2 id=&#34;architecture&#34;&gt;Architecture&lt;/h2&gt;&#xA;&lt;figure class=&#34;architecture&#34; aria-labelledby=&#34;arch-robot-task-planner-2&#34;&gt;&#xA;  &lt;figcaption class=&#34;architecture__title&#34; id=&#34;arch-robot-task-planner-2&#34;&gt;Component overview&lt;/figcaption&gt;&#xA;    &lt;pre class=&#34;architecture__sketch&#34;&gt;&lt;code&gt;  [1] Action schema&#xA;  [2] Feasibility validator&#xA;  [3] Human confirmation gate&#xA;  [4] Simulation harness&#xA;  [5] Inference backend&lt;/code&gt;&lt;/pre&gt;&lt;p class=&#34;architecture__caption&#34;&gt;A concrete architecture diagram will replace this sketch when the blueprint is published.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Teleoperation Copilot</title>
      <link>https://ait.bsc.es/blueprints/teleoperation-copilot/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/teleoperation-copilot/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;A monitoring assistant that summarizes robot telemetry for a human operator during teleoperation.&lt;/p&gt;&#xA;&lt;p&gt;This page shows the structure a blueprint detail page uses. The problem statement and component list below are real design context; the deployment and usage sections are placeholders.&lt;/p&gt;&#xA;&lt;h2 id=&#34;problem-addressed&#34;&gt;Problem addressed&lt;/h2&gt;&#xA;&lt;p&gt;A teleoperation operator watching many telemetry streams cannot attend to all of them, and the signal that matters is usually a correlation across several rather than a single threshold breach.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
