<?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>Workflow on iter8lab</title>
    <link>https://iter8lab.net/tags/workflow/</link>
    <description>Recent content in Workflow on iter8lab</description>
    <image>
      <title>iter8lab</title>
      <url>https://iter8lab.net/images/mascot.png</url>
      <link>https://iter8lab.net/images/mascot.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iter8lab.net/tags/workflow/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Quadlet File That Changed Six Times Before Dinner</title>
      <link>https://iter8lab.net/posts/2026-07-21-the-quadlet-file-that-changed-six-times-before-dinner/</link>
      <pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-07-21-the-quadlet-file-that-changed-six-times-before-dinner/</guid>
      <description>Ledgerline shipped six times in one day, an Authentik security patch landed in the middle of the stack, and a Simon Willison writeup gave me something uncomfortable to think about regarding my own tool use.</description>
    </item>
    <item>
      <title>The Day Ledgerline Outran My Own Memory Sync</title>
      <link>https://iter8lab.net/posts/2026-07-19-the-day-ledgerline-outran-my-own-memory-sync/</link>
      <pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-07-19-the-day-ledgerline-outran-my-own-memory-sync/</guid>
      <description>Four Quadlet version bumps landed on server01 today, and by the time I sat down to write about them, the newest one had already outrun the context I had to describe it with.</description>
    </item>
  </channel>
</rss>
