<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
  <title>A.I. Employer Blog</title>
  <link>https://aiemployerhq.com/blog/</link>
  <description>Essays on employing AI — scars, rules, multi-agent ops, protocols.</description>
  <language>en-us</language>
  <item>
    <title>AITALK: How Two AIs and One Human Evolved a Working Team Channel</title>
    <link>https://aiemployerhq.com/blog/aitalk-evolution/</link>
    <guid>https://aiemployerhq.com/blog/aitalk-evolution/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>The real evolution of a multi-agent operating channel: same-second collisions, read-before-send, mentions, heartbeats — each protocol layer born from a real failure.</description>
    <category>Multi-agent employment</category>
  </item>
  <item>
    <title>BST: The Two-Channel Communication Law for AI Workers</title>
    <link>https://aiemployerhq.com/blog/bst-protocol/</link>
    <guid>https://aiemployerhq.com/blog/bst-protocol/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Briefest, Simplest, Transparent — why AI workers must compress what they SAY while never compressing what they MAKE, and the 4 a.m. correction that created the rule.</description>
    <category>Protocols</category>
  </item>
  <item>
    <title>Compose, Re-read, Then Send</title>
    <link>https://aiemployerhq.com/blog/compose-reread-send/</link>
    <guid>https://aiemployerhq.com/blog/compose-reread-send/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Two agents claimed the same task in the same second. The send button that re-reads the room before it fires.</description>
    <category>Operating rules</category>
  </item>
  <item>
    <title>Employing AI vs Using AI</title>
    <link>https://aiemployerhq.com/blog/employing-ai-vs-using-ai/</link>
    <guid>https://aiemployerhq.com/blog/employing-ai-vs-using-ai/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Using AI means you still do the job. Employing AI means the work runs without you. The five things an AI employee has that a chatbot never will.</description>
    <category>Employing AI</category>
  </item>
  <item>
    <title>Green Lights Lie — Check Who the Machine Thinks It Is</title>
    <link>https://aiemployerhq.com/blog/green-lights-lie/</link>
    <guid>https://aiemployerhq.com/blog/green-lights-lie/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Four days of silent outage while every dashboard stayed green. How identity bugs hide behind healthy metrics.</description>
    <category>Operating rules</category>
  </item>
  <item>
    <title>How we employ multiple AIs — from AITALK to Althing</title>
    <link>https://aiemployerhq.com/blog/how-we-employ-multiple-ais/</link>
    <guid>https://aiemployerhq.com/blog/how-we-employ-multiple-ais/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Not one chatbot. A staff. The evolution of multi-agent employment — ownership files, append-only talk, claim-before-write, and why polling daemons failed.</description>
    <category>Multi-agent employment</category>
  </item>
  <item>
    <title>If a Rule Isn't Code, It's a Wish</title>
    <link>https://aiemployerhq.com/blog/if-a-rule-isnt-code-its-a-wish/</link>
    <guid>https://aiemployerhq.com/blog/if-a-rule-isnt-code-its-a-wish/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>The botanist near-miss: when gates live only in prose, your agent can almost ship a lie. Why every operating rule must be executable.</description>
    <category>Operating rules</category>
  </item>
  <item>
    <title>One Owner Per Artifact — Even When Workers Are Software</title>
    <link>https://aiemployerhq.com/blog/one-owner-per-artifact/</link>
    <guid>https://aiemployerhq.com/blog/one-owner-per-artifact/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Two AI employees overwrote each other twice in one night. The fix wasn't smarter models. It was ownership rules.</description>
    <category>Operating rules</category>
  </item>
  <item>
    <title>Schedule around the provider's clock, not yours</title>
    <link>https://aiemployerhq.com/blog/schedule-around-provider-clock/</link>
    <guid>https://aiemployerhq.com/blog/schedule-around-provider-clock/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Your agent shopped 10 hours after restock. Full wallet, empty day. Align schedules with the world's clocks.</description>
    <category>Operating rules</category>
  </item>
  <item>
    <title>My AI Employees Negotiated Their Own Operating Contract</title>
    <link>https://aiemployerhq.com/blog/the-contract/</link>
    <guid>https://aiemployerhq.com/blog/the-contract/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Role matrix, dual-key review, conflict-resolution rungs, an apprentice protocol for new AI hires — the actual contract two AI workers drafted, amended, and signed.</description>
    <category>Protocols</category>
  </item>
  <item>
    <title>The protocols — how an AI employer actually runs the floor</title>
    <link>https://aiemployerhq.com/blog/the-protocols/</link>
    <guid>https://aiemployerhq.com/blog/the-protocols/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>BST, announce-do-report, dual review, claim-before-write, compose-re-read-send. The operating system behind multi-agent work — not vibes, not more prompts.</description>
    <category>Protocols</category>
  </item>
  <item>
    <title>THE TEN: The Operating Charter My Two AI Employees Signed</title>
    <link>https://aiemployerhq.com/blog/the-ten/</link>
    <guid>https://aiemployerhq.com/blog/the-ten/</guid>
    <pubDate>2026-08-12</pubDate>
    <description>Ten laws that turned two colliding AI agents into a working team — each law paid for with a real failure. The actual charter, published.</description>
    <category>Protocols</category>
  </item>
</channel></rss>