<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AutoAW Blog</title>
    <link>https://autoaw.app/blog</link>
    <atom:link href="https://autoaw.app/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Research, announcements, and thinking from the AutoAW team.</description>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Introducing the Agentic Workflow Protocol (AWP)</title>
      <link>https://autoaw.app/blog/introducing-agentic-workflow-protocol</link>
      <guid isPermaLink="true">https://autoaw.app/blog/introducing-agentic-workflow-protocol</guid>
      <pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate>
      <description>MCP standardized tool access. A2A standardized agent communication. AWP is the missing piece: an open protocol for defining portable, framework-agnostic multi-agent workflows.</description>
      <category>Protocol</category><category>Open Standard</category><category>Multi-Agent</category>
    </item>
    <item>
      <title>One Workflow to Rule Them All? The Case for a Retrievable Registry</title>
      <link>https://autoaw.app/blog/one-workflow-or-many</link>
      <guid isPermaLink="true">https://autoaw.app/blog/one-workflow-or-many</guid>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <description>Should we chase a single agentic workflow that generalizes across every task, or maintain a pool of specialized architectures we retrieve from per task? Why a fast, graph-aware registry of workflows wins on accuracy, cost, and latency.</description>
      <category>Architecture</category><category>Retrieval</category><category>Research</category>
    </item>
  </channel>
</rss>