<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
  <title>Notes | Async Digital</title>
  <subtitle>Working notes on building software with AI agents doing a large share of the work. The subject is the system around the model rather than the model itself, and the code underneath both: how sessions coordinate, where the rules live, and which checks can actually fail.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://async-digital.com/notes/feed.xml" />
  <link rel="alternate" type="text/html" href="https://async-digital.com/notes/" />
  <id>https://async-digital.com/notes/feed.xml</id>
  <updated>2026-09-15T00:00:00Z</updated>
  <entry>
    <title>Holding it right</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/holding-it-right/" />
    <id>https://async-digital.com/notes/holding-it-right/</id>
    <published>2026-09-15T00:00:00Z</published>
    <updated>2026-09-15T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>One talk made a weak model do a real job with a harness. The other says no harness fixes what agents do to a codebase. I stopped reading every line, so I checked where my own checks stop.</summary>
  </entry>
  <entry>
    <title>One line, fourteen packages</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/one-line-fourteen-packages/" />
    <id>https://async-digital.com/notes/one-line-fourteen-packages/</id>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>One dependency line pulled 14 packages and about 40,000 lines of code into the app. Apple closed most of the gaps and an agent writes most of the boilerplate now, so what does a third-party architecture still buy?</summary>
  </entry>
  <entry>
    <title>One caller hid the crash</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/one-caller-hid-the-crash/" />
    <id>https://async-digital.com/notes/one-caller-hid-the-crash/</id>
    <published>2026-09-11T00:00:00Z</published>
    <updated>2026-09-11T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>A test suite passed seven out of seven while the code under it corrupted the task allocator on every run. Only one file called the initialiser that triggers it, and the bug needs two.</summary>
  </entry>
  <entry>
    <title>Asking if it's finished strips the lock</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/asking-strips-the-lock/" />
    <id>https://async-digital.com/notes/asking-strips-the-lock/</id>
    <published>2026-08-30T00:00:00Z</published>
    <updated>2026-08-30T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>The polite way to coordinate two AI sessions sharing one save file, asking whether it has finished, is the message that strips its protection. I caused the bug live while researching it.</summary>
  </entry>
  <entry>
    <title>A correction looks like a duplicate</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/a-correction-looks-like-a-duplicate/" />
    <id>https://async-digital.com/notes/a-correction-looks-like-a-duplicate/</id>
    <published>2026-08-30T00:00:00Z</published>
    <updated>2026-08-30T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>A file my agents keep said the opposite of the truth about my own machine for weeks. A June paper measures why corrections get thrown away by the check meant to stop duplicates.</summary>
  </entry>
  <entry>
    <title>The template wrote the ticket</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/the-template-wrote-the-ticket/" />
    <id>https://async-digital.com/notes/the-template-wrote-the-ticket/</id>
    <published>2026-08-20T00:00:00Z</published>
    <updated>2026-08-20T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>An agent filed nine paragraphs to change two words in a comment. It had followed its instructions exactly.</summary>
  </entry>
  <entry>
    <title>Coordination lives in the harness, not the prompt</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/coordination-lives-in-the-harness/" />
    <id>https://async-digital.com/notes/coordination-lives-in-the-harness/</id>
    <published>2026-08-05T00:00:00Z</published>
    <updated>2026-08-05T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>A session hands itself off to the next one, and won’t trample work another session is already doing. Neither behaviour is a prompt.</summary>
  </entry>
  <entry>
    <title>Your rules should travel with you</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/your-rules-should-travel-with-you/" />
    <id>https://async-digital.com/notes/your-rules-should-travel-with-you/</id>
    <published>2026-05-18T00:00:00Z</published>
    <updated>2026-05-18T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>The rules you build with an AI assistant are professional capital. They belong to the studio, not the vendor.</summary>
  </entry>
  <entry>
    <title>Notes on coordinating AI agent swarms</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/coordinating-ai-agent-swarms/" />
    <id>https://async-digital.com/notes/coordinating-ai-agent-swarms/</id>
    <published>2026-05-02T00:00:00Z</published>
    <updated>2026-05-02T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>The primitives missing from agent-swarm runtimes, and the disciplines that fill the gap.</summary>
  </entry>
  <entry>
    <title>Thirty days of agentic development</title>
    <link rel="alternate" type="text/html" href="https://async-digital.com/notes/thirty-days-of-agentic-development/" />
    <id>https://async-digital.com/notes/thirty-days-of-agentic-development/</id>
    <published>2026-04-24T00:00:00Z</published>
    <updated>2026-04-24T00:00:00Z</updated>
    <author><name>Rob Nash</name></author>
    <summary>I counted what thirty days with an AI coworker actually produced, because I could not find an honest figure to compare against.</summary>
  </entry>
</feed>
