<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Meta on Eventually Consistent</title>
    <link>https://eventually-consistent.io/tags/meta/</link>
    <description>Recent content in Meta on Eventually Consistent</description>
    <image>
      <title>Eventually Consistent</title>
      <url>https://eventually-consistent.io/img/og-default.png</url>
      <link>https://eventually-consistent.io/img/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://eventually-consistent.io/tags/meta/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Community Is the Design Review: Six Articles, Four Phases, One Night</title>
      <link>https://eventually-consistent.io/posts/the-community-is-the-design-review/</link>
      <pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://eventually-consistent.io/posts/the-community-is-the-design-review/</guid>
      <description>One evening on dev.to turned into four new phases on cairn&amp;rsquo;s roadmap, three new global rules on my machine, and four issues shipped the same week. The mechanism was reading other people&amp;rsquo;s write-ups as bug reports against my own code. Here&amp;rsquo;s the loop, the receipts, and the people to thank.</description>
    </item>
    <item>
      <title>The Harness Runs Itself: Budgeted, Headless, and Honest About Its Own Bugs</title>
      <link>https://eventually-consistent.io/posts/the-harness-runs-itself/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://eventually-consistent.io/posts/the-harness-runs-itself/</guid>
      <description>Four weeks after the work-harness post: cairn learned to keep its own documentation honest, run entire phases unattended inside a token budget, and — twice now — catch its own bugs in the act and ship the fixes. Here&amp;rsquo;s what a self-running work harness actually looks like, receipts included.</description>
    </item>
    <item>
      <title>The Work Harness: What Cairn Became, and the Competitor It Grew Up Into</title>
      <link>https://eventually-consistent.io/posts/the-work-harness/</link>
      <pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://eventually-consistent.io/posts/the-work-harness/</guid>
      <description>Six weeks of shipping turned cairn from a wrapper around other people&amp;rsquo;s tools into a full work harness — a four-vendor AI review council, a portfolio board, a platform-native rebuild, and the honest answer to the question that review surfaced: who is cairn actually competing with?</description>
    </item>
    <item>
      <title>Four Tools in Three Weeks: What Building With AI Actually Looked Like</title>
      <link>https://eventually-consistent.io/posts/four-tools-three-weeks/</link>
      <pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://eventually-consistent.io/posts/four-tools-three-weeks/</guid>
      <description>Four real products — a multi-cloud tag and storage tool, a resume tailor, an OKR tracker, and the planning system underneath all of it — built and shipped in about three weeks. What made it fast, what I got wrong, and what AI still can&amp;rsquo;t do for you.</description>
    </item>
    <item>
      <title>Hello World! Welcome to Eventually Consistent</title>
      <link>https://eventually-consistent.io/posts/hello-eventually-consistent/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://eventually-consistent.io/posts/hello-eventually-consistent/</guid>
      <description>Why this blog exists and what I&amp;rsquo;ll write about here.</description>
    </item>
  </channel>
</rss>
