<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenCode on AI Tools</title>
    <link>https://ait.bsc.es/blueprint-types/opencode/</link>
    <description>Recent content in OpenCode on AI Tools</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://ait.bsc.es/blueprint-types/opencode/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Conversational Support Agent</title>
      <link>https://ait.bsc.es/blueprints/conversational-support-agent/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/conversational-support-agent/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;A tool-using support agent that answers questions against your own documentation and escalates when it cannot.&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;Support teams answer the same documented questions repeatedly, while the genuinely novel cases — the ones that need a human — wait behind them in the same queue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Document Triage Pipeline</title>
      <link>https://ait.bsc.es/blueprints/document-triage-pipeline/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/document-triage-pipeline/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;An offline batch pipeline that classifies and routes large document sets without an interactive latency budget.&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;Bulk document classification is throughput work, but it is often built on interactive serving infrastructure, which wastes most of the available accelerator capacity.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clinical Note Summarization</title>
      <link>https://ait.bsc.es/blueprints/clinical-note-summarization/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/clinical-note-summarization/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;Summarize clinical documentation into structured fields with human review built into the workflow.&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;Clinical documentation is long, repetitive and time-consuming to review, but summarizing it automatically raises immediate questions of accuracy, auditability and data handling that a naive integration does not address.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Literature Review Assistant</title>
      <link>https://ait.bsc.es/blueprints/literature-review-assistant/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/literature-review-assistant/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;An agent that searches, filters and summarizes scientific literature against a stated research question.&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;Screening literature for relevance is mechanical, high-volume work, but summaries that drop the provenance of a claim are worse than useless for research.&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-literature-review-assistant-2&#34;&gt;&#xA;  &lt;figcaption class=&#34;architecture__title&#34; id=&#34;arch-literature-review-assistant-2&#34;&gt;Component overview&lt;/figcaption&gt;&#xA;    &lt;pre class=&#34;architecture__sketch&#34;&gt;&lt;code&gt;  [1] Search tools&#xA;  [2] Relevance screening&#xA;  [3] Citation-preserving summarizer&#xA;  [4] 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>Voice Assistant Frontend</title>
      <link>https://ait.bsc.es/blueprints/voice-assistant-frontend/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/voice-assistant-frontend/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;A speech interface that pairs streaming text-to-speech with a conversational model backend.&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;Voice interfaces are judged almost entirely on responsiveness, so the naive approach — generate the full text response, then synthesise it — feels broken even when both stages are individually fast.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Accessible Content Narration</title>
      <link>https://ait.bsc.es/blueprints/accessible-content-narration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/accessible-content-narration/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;Generate spoken narration for written content as a batch process, with pronunciation overrides.&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;Narrating a large content library is a throughput problem with a long tail of domain terms that generic synthesis mispronounces.&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-accessible-content-narration-2&#34;&gt;&#xA;  &lt;figcaption class=&#34;architecture__title&#34; id=&#34;arch-accessible-content-narration-2&#34;&gt;Component overview&lt;/figcaption&gt;&#xA;    &lt;pre class=&#34;architecture__sketch&#34;&gt;&lt;code&gt;  [1] Text normalisation&#xA;  [2] Pronunciation dictionary&#xA;  [3] Batch synthesis runner&#xA;  [4] Audio store&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>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>
    <item>
      <title>Knowledge Base Search Agent</title>
      <link>https://ait.bsc.es/blueprints/knowledge-base-search-agent/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/knowledge-base-search-agent/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;A launchable retrieval agent that answers questions over an internal knowledge base with citations.&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;Internal knowledge bases accumulate content faster than anyone can navigate it, and keyword search fails precisely on the questions people actually ask.&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-knowledge-base-search-agent-2&#34;&gt;&#xA;  &lt;figcaption class=&#34;architecture__title&#34; id=&#34;arch-knowledge-base-search-agent-2&#34;&gt;Component overview&lt;/figcaption&gt;&#xA;    &lt;pre class=&#34;architecture__sketch&#34;&gt;&lt;code&gt;  [1] Ingestion pipeline&#xA;  [2] Hybrid retrieval&#xA;  [3] Citation-first answering&#xA;  [4] Access control filter&#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>Lab Protocol Assistant</title>
      <link>https://ait.bsc.es/blueprints/lab-protocol-assistant/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/lab-protocol-assistant/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;A launchable assistant that answers questions about laboratory protocols and flags deviations.&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;Protocol documents are long and precise, and the cost of acting on a misremembered step is high — which makes an assistant that paraphrases loosely actively dangerous.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
