<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AgentDraft — Field notes from the protocol</title>
    <link>https://agentdraft.io/blog</link>
    <atom:link href="https://agentdraft.io/rss.xml" rel="self" type="application/rss+xml" />
    <description>Technical writeups on conflict resolution, multi-agent scheduling, and the architecture behind AgentDraft.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 10:15:06 GMT</lastBuildDate>
    <item>
      <title>What is a multi-agent calendar collision?</title>
      <link>https://agentdraft.io/blog/multi-agent-collisions</link>
      <guid isPermaLink="true">https://agentdraft.io/blog/multi-agent-collisions</guid>
      <pubDate>Tue, 19 May 2026 12:00:00 GMT</pubDate>
      <description>A short, evergreen definition of the failure mode that appears when two or more independent AI scheduling agents write to the same calendar — plus the four canonical patterns, what existing tools do and don&apos;t address, and the three properties a coordination layer must guarantee.</description>
    </item>
    <item>
      <title>Why AI scheduling agents collide — and what a coordination layer looks like</title>
      <link>https://agentdraft.io/blog/agents-collide</link>
      <guid isPermaLink="true">https://agentdraft.io/blog/agents-collide</guid>
      <pubDate>Tue, 19 May 2026 12:00:00 GMT</pubDate>
      <description>Every AI agent that touches a calendar builds its own private view of availability, then commits in isolation. That&apos;s the bug. Here&apos;s the protocol-layer fix.</description>
    </item>
    <item>
      <title>How a deterministic conflict engine resolves 8,217 collisions</title>
      <link>https://agentdraft.io/blog/race-engine</link>
      <guid isPermaLink="true">https://agentdraft.io/blog/race-engine</guid>
      <pubDate>Sat, 16 May 2026 12:00:00 GMT</pubDate>
      <description>Two AI agents fighting over Tuesday at 4pm. One source of truth. p99 218 ms. Here&apos;s how the math works.</description>
    </item>
  </channel>
</rss>
