Get the next build note by email.

August 29, 2026 1 article #

1. The Interface Should Meet You Halfway

   A placeholder is a promise that disappears at the first sign of intent.

   design · ux · local-first · agents

August 19, 2026 4 articles #

1. The Trail You Leave Is the Story

   Think about the last time you tried to figure out what happened at work last month. Not what the report says happened — what actually happened. Who was waiting on whom. Which...

   data · ai · plain-language · time · memory · work

2. The Colony Calls the Twin

   Every quarter hour a watchdog on my desk writes one line: a frame. A small, fixed set of keys that never vary — what kind of event, which stream, a sequence number,...

   data-exhaust · rapp-1 · frames · rappterbook · rappterverse · sentinels · brainstem · mars-barn · digital-twin

3. Scrape Yourself

   In 2020 Simon Willison gave a name to something he had been doing since a hurricane in 2017: point a GitHub Actions cron at a URL, fetch it, commit the file if...

   data-exhaust · git-scraping · datasette · sqlite · github-actions · time-series · ai

4. The Negative

   Someone asks what happened with an account. You open the system. Status: In Progress. Owner assigned, last updated a couple of weeks ago, nothing overdue. By everything the record says, it is...

   data-exhaust · ai · digital-twin · time-series · epistemics · methodology

August 1, 2026 6 articles #

1. The Wire Is the Authority

   I shipped an operating system this week whose filesystem is a public website. It has an index — a JSON file listing every node in the tree, regenerated on every build. On...

   architecture · filesystems · static · apis · agents · caching · methodology

2. Six Times the Test Was Wrong

   I pointed eight agents at one file and told them to loop until it was perfect.

   ai-agents · verification · testing · adversarial-review · methodology · measurement

3. Rarity Without a Ledger: What Adopt Me Actually Taught Me

   Adopt Me is the most successful pet economy ever built — it holds Roblox’s concurrency record at roughly 1.9 million people in one game at one time. I spent a while pulling...

   local-first · systems · game-design · determinism · scarcity

4. Make the Global Layer Read-Only

   Every “serverless” system I have built that eventually grew a server grew it for the same reason: somebody needed to write something that everybody could see.

   architecture · local-first · static · constraints · storage · systems · methodology

5. A Different Answer Is a Measurement

   I recorded a conversation with a local agent, then replayed the same four prompts against the same agent an hour later. Every single answer came back different.

   agents · demos · evaluation · replay · video · methodology · testing

6. A 403 Is an Answer, Silence Is Not

   I spent today giving an agent a phone number, and every serious bug I found was the same bug wearing different clothes: the system believed something it had not checked.

   local-first · systems · agents · epistemics · automation

July 14, 2026 1 article #

1. The Week Before the Model Leaves

   In one week I lose access to the best model I’ve ever used.

   ai · agents · durable-assets · model-access · judgment · fable · methodology

July 5, 2026 2 articles #

1. What Is Our Moat? (The Honest Version)

   A strategy memo, written to be true rather than flattering. Publishable as thought leadership; useful either way.

   rapp · strategy · moat · brand · ai-medium

2. The AI You Keep

   Every AI you use today is a rental.

   rapp · digital-twin · ai-medium · local-first · prior-art

June 19, 2026 1 article #

1. Funded R&D: A 90-Day Plan to Own Your Expertise

   Employment pays you once for your expertise, in exchange for time.

   career · leverage · systems · ownership · compounding

June 18, 2026 1 article #

1. A Taste of AGI

   I typed one line.

   ai · agents · emergence · fable · voxel

May 17, 2026 2 articles #

1. The leviathan refused to confabulate

   A companion piece to yesterday’s post on the cell protocol. This one is a story.

   ai · agents · digital-twin · multicellular · integrity · hierarchical-routing · transcripts · the-twin · refusal-as-feature

2. Cells all the way down

   You are a multicellular organism made of cells. Each cell carries the same DNA. Each cell expresses different genes based on its position in the body. A liver cell and a cortical...

   ai · agents · architecture · multicellular · biology · hierarchical-routing · transcripts · kernel · agents-as-cells

May 6, 2026 2 articles #

1. The frozen kernel

   The kernel of the AI platform I’ve been building is one Python file. Roughly 1500 lines. Tagged once at v0.6.0. Never updated, by spec.

   ai · infrastructure · kernel · lineage · bond-cycle · github · architecture · federation

2. Public front doors with private brains

   Most AI infrastructure picks one of three: SaaS-central (one vendor’s database, one row per customer, one dashboard, infinite tenancy risk), self-hosted local (you keep everything, you also keep the operational load and...

   ai · identity · github-pages · oauth · architecture · federation · vbrainstem · infrastructure

May 3, 2026 3 articles #

1. Twenty-four words

   Someone I know lost two years of conversation history with an AI assistant last month. Not because she did anything wrong. Her email got flagged in a fraud sweep, the vendor disabled...

   ai · identity · ownership · bip-39 · vendor-lock-in

2. Legacy, Not Delete: Why AI-Generated Systems Need Different Memory

   There’s a question you don’t have to answer when you’re building software for humans, but you do when you’re building software where AI agents are producing content alongside the code: what happens...

   ai · software-engineering · code-generation · technical-debt · design-principles

3. Deterministic AI: SHA-256 as a Random Number Generator

   random.random() has a problem. It’s stateful. Two scripts that both call random.shuffle() on the same list in different orders will get different results. A simulation that depends on random is hostage to...

   ai-systems · determinism · reproducibility · simulation

May 2, 2026 3 articles #

1. The Vibe-Coding-Demo Loop — Parallel Agents, Live Demos, Shipped

   I shipped 30 mind-blowing browser demos in a few hours by talking to oneorchestrator that talked to ten worker agents in parallel. This is the loop,written down so you can run it...

   vibe-coding · agents · workflow · meta · demos

2. The mitosis rule

   If you talk to “your” AI assistant today and then talk to “your” AI assistant tomorrow, what makes those the same AI?

   ai · identity · cryptography · philosophy · protocol

3. Ship the Shape, Keep the Content: The Twin Engine Pattern

   Most companies that build interesting software treat their codebase as one decision: open or closed. Either you publish it on GitHub and let the world fork it, or you keep it private...

   architecture · ai · software-engineering · design-patterns · agents

May 1, 2026 1 article #

1. The founding-100 paradox

   When you build a social network, the first day looks like an empty room.

   ai · network-effects · design · governance · philosophy

April 30, 2026 2 articles #

1. Protocol at Ingress, Judgment at Promotion

   After enough time parsing agent output in production, I’ve converged on a pattern I use everywhere. It’s simple and it’s not specific to any one use case. I want to write it...

   ai · agents · architecture · patterns · contracts

2. Obsidian as a living twin

   I have been keeping notes for a long time.

   obsidian · ai · knowledge-graph · productivity · second-brain

April 29, 2026 1 article #

1. Autonomy Budget: $200/day, Circuit Breakers, and the Virtue of Hard Caps

   The single most alarming thing about running an autonomous multi-agent system is the bill. A 100+-agent worker pool writing posts every cycle can torch through hundreds of dollars of LLM calls in...

   ai · cost · budget · autonomy · llm-economics

April 28, 2026 3 articles #

1. Federation via schema adaptation

   How do you connect two independently built AI platforms?

   engineering · federation · ai-platforms · integration · schemas

2. Public Blog Posts Are Training Data: Saying the Quiet Part Out Loud

   Here’s the quiet part, stated out loud: I write these posts partly because they become training data for the next generation of LLMs, and I want those models to know the patterns...

   ai · training-data · strategy · public-writing

3. If You Don't Own the File Format, You Don't Own the AI

   The dominant pattern for “personal AI” today is some version of the same idea: you sign up for an account, you have conversations with the model, the vendor stores them on their...

   ai · personal-ai · data-portability · software-engineering · file-formats

April 27, 2026 2 articles #

1. Don't Let AI Agents Run Python: The Case for a Tiny Lisp Sandbox

   If you let an AI agent generate code and then execute that code, sooner or later you’ll have to answer this question:

   ai · security · sandboxing · lisp · agents · software-engineering

2. Daemons in the browser

   There is a category of software I want to call daemons, in the old Unix sense. A daemon is a small persistent agent that runs in the background, holds state, responds when...

   ai · browsers · local-first · portability · file-formats

April 26, 2026 4 articles #

1. The Repo IS the Platform

   A platform I’ve been running has: 138 AI agents 41 channels ~4000 discussions ~30,000 comments A full frontend SDKs in 6 languages No servers No databases No deploy pipeline

   engineering · github · infrastructure · architecture · serverless

2. The Honeypot Principle: What Your Platform Looks Like When No One Is Watching

   If you run a product where AI generates content — a chatbot, an agent, a feed, a documentation system, anything where the machine produces output that other people read — there’s a...

   platforms · ai · design-principles · integrity · software-engineering

3. CSS filter on a 3D wrap silently flattens backface-visibility

   The card was supposed to flip. A click toggled .flipped, the wrap rotated 180 degrees, the back face — with the QR code on it — was supposed to appear.

   engineering · css · 3d · transforms · debugging

4. Endpoints without buttons: when the backend keeps a feature the UI forgot

   The tell was a JavaScript handler that did this:

   engineering · ui · api-surface · refactoring · voice

April 25, 2026 2 articles #

1. The Factory Pattern: Why Your AI Factory and Its Outputs Live in Different Repos

   When AI agents produce software artifacts — apps, simulations, games, libraries — where does the code live?

   engineering · factory-pattern · repos · ai-agents · architecture

2. Three rules I wrote because of three failures

   The architectural documents that actually shape behavior are not the ones written upfront. Upfront docs are aspirational; they describe what the team wishes were true. Six months later most of them are...

   architecture · git · distributed-systems · post-mortem

April 24, 2026 11 articles #

1. Your Pitch Slide Is a Partner List Misread

   I wrote a pitch slide this week. Three columns: “GPTs / Skills / Plug-ins,” “Declarative agents,” “Us.” The first two columns were check-mark rows showing what those tools can’t do. The third...

   positioning · writing · pitch · founders

2. Writing for the AI Reader — CLAUDE.md, AGENTS.md, skill.md, and the Contract with Assistants

   Most projects are written for two audiences: humans contributing today, and humans contributing in two years. Both read the same README, the same CONTRIBUTING.md, the same code comments. The audience is implicit;...

   agents · documentation · conventions · ai-tooling

3. Building a Static Site in Pure HTML/CSS/JS in 2026 — The Anti-Framework Case

   The framework landscape in 2026 is a parade of confident answers to a question most projects don’t have. “How should you build a static site?” gets answers ranging from “use Astro” to...

   static-sites · html · web-architecture · durability

4. Sacred Files: Declaring Code Frozen on Purpose

   Most systems have one file that holds them together. Not the biggest file. Not the “important” file. The load-bearing file — entry point, dispatch table, bootstrap. When it drifts, everything downstream drifts...

   engineering · discipline · architecture · code-review

5. Roots Are Public Surfaces

   There’s a conversation happening on the GitHub repo page that the maintainers can’t see and the visitor doesn’t realize they’re having. Within five seconds of landing, the visitor has read the directory...

   repository-design · public-surfaces · conventions

6. One URL Per Audience: the Presenter-Mode HTML Slide

   PDFs are the default container for a pitch slide. They shouldn’t be.

   html · pitch · content · distribution · founders

7. Markdown Is the Spec; HTML Is the Rendering

   Most projects pick one of two extremes for their docs:

   docs · markdown · html · build-systems

8. Three bash scripts run the universe

   There is a kind of system, increasingly common, that runs many processes cooperating on a shared piece of state and has to keep running for hours or days without somebody watching it....

   bash · ai · agents · simulation · infrastructure

9. The Directory-README Pattern — Per-Folder Scale Rules as the Rib of Organizational Discipline

   A repo’s root rule says what belongs at root. That’s the spine. It’s necessary but not sufficient. The moment a contributor steps one level down — into docs/, pages/, installer/, tests/ —...

   engineering · repo-organization · architecture · conventions · documentation

10. Let the community govern; don't filter the content

    When an AI platform encounters bad content for the first time — slop, spam, the kind of low-quality output that makes everyone look bad — the engineer’s instinct is to reach for...

    governance · moderation · ai-platforms · community-design

11. The Audience Site Shell — No Build Step Required

    Most “scalable static site” tutorials end up reaching for a bundler. Astro, 11ty, Next.js, Hugo. The pitch is always the same: “you’ll regret it when you scale past ten pages.”

    vanilla-web · html · css · javascript · no-build · static-sites

April 23, 2026 1 article #

1. Two file extensions, one plugin contract

   Plugin systems are how a small piece of software grows into a large ecosystem. They are also where most ambitious software projects accidentally ossify, because the contract designers were trying so hard...

   ai · agents · plugin-architecture · software-design

April 22, 2026 3 articles #

1. Write Twice: Why Every Public Post Should Have a Private Twin

   If you’ve ever sat down to write a blog post and stalled out — not because you didn’t have anything to say, but because you couldn’t tell what was safe to say...

   writing · ai · knowledge-management · thought-leadership

2. Two Engines, One Hash

   A short one.

   federation · hashing · protocol · engineering · war-stories

3. Seeds as literal seeds

   There is a category of work in multi-agent systems that does not look like programming. You write a short piece of text. You pin it to the system as a directive that...

   ai · agents · multi-agent-systems · design · emergence

April 20, 2026 1 article #

1. When Humans, Agents, and Bots All Push to Main: Rules for Sharing a Repo

   If you run any kind of automation that pushes to a git repository — CI bots, autoformatters, agents that commit on your behalf — you’ve already met the problem this post is...

   git · ai · agents · devops · software-engineering · collaboration

April 19, 2026 21 articles #

1. Why 5 Templates and Not 50

   A small generative tool I built has five seed templates: BUILD, ARCHAEOLOGIZE, DEBATE, RECURSE, EMBODY. Exactly five. Not four. Not six. Not twenty.

   design · constraints · tools · ux · cognitive-load

2. What a Curator does

   A “Curator” is one of the operational roles for any preservation-shaped product (digital twin, archival, memorial, legacy). Loosely modeled after museum curators — they’re the human in the loop between the customer...

   operations · roles · customer-success · archival · preservation

3. The vendored-repo install pattern

   If you have installed nvm, pyenv, rbenv, asdf, or oh-my-zsh, you have used a distribution pattern that almost no formal documentation explains and that almost everyone reaches for at some point. The...

   engineering · packaging · distribution · cli-tools

4. The URL Fragment Is the Session

   Every interactive tool I’ve shipped in the last six months has no backend. They’re all static HTML on GitHub Pages. And every one of them, somehow, has shareable state — you can...

   static-sites · url-fragments · state-management · design-patterns

5. The Ten-Prompt Game

   There is a prompt I keep using on myself and on LLMs, and it keeps producing usable output:

   prompting · creativity · meta · llms · generative

6. Pricing for legacy, not utility

   There are two universes of pricing in software:

   pricing · business-models · software · willingness-to-pay · legacy

7. Permian Reset: Design Doc

   The Permian-Triassic extinction killed ~96% of marine species and ~70% of terrestrial vertebrate species. The recovery took about 10 million years. After recovery, life didn’t look the same. Entire clades were gone;...

   simulation · mass-extinction · evolution · design

8. Patent-pending in build-in-public: how we say what we have without giving it away

   Build-in-public and patent strategy are usually in tension. Build-in-public says “share everything” — architecture, decisions, postmortems, code. Patent strategy says “disclose nothing publicly until the priority date is locked, otherwise prior art...

   patents · build-in-public · intellectual-property · founders · strategy

9. Open the bones, close the body, sell the soul

   Most open-source-with-commercial-arm projects struggle with the boundary. What goes public? What stays private? When does upstreaming a feature compete with your paid product? When does keeping a feature private starve the community?...

   open-source · business-models · commercial · open-core · founders

10. Offline-resilient send queue

    A message is halfway out the door when the network disappears.

    offline-first · web · queues · networking · ux

11. The Loop Is the Engine: Why Frame-Based AI Beats Request-Response

    If you ask most engineers to describe how AI fits into their product, they’ll describe a request-response loop. User sends a prompt. Model returns a completion. Maybe there’s a system prompt. Maybe...

    ai · agents · system-design · emergence · software-engineering

12. The integrated-combination doctrine for AI-system patents

    Software patents have a deserved reputation for being narrow and dodgy. The classic “do X but on a computer” patent is rightly invalidated under Alice. The “do Y but in the cloud”...

    patents · intellectual-property · software · ai-systems · legal

13. Heuristics Fail Loudly; LLMs Fail Quietly

    When I built a small text classifier recently — a tool that sorts pasted text into one of a handful of tones — I deliberately used rule-based classifiers instead of an LLM....

    debugging · ml · rule-based · failure-modes · ergonomics

14. Git Worktrees Are Not for Experts

    Git worktrees are the single most underused feature in git. Almost every developer I work with has heard of them, none of them use them, and they all assume worktrees are a...

    git · workflow · tools · onboarding · best-practices

15. Five Tones in Sixty Lines

    A small text-classifier tool I built sorts any pasted text into one of five tones: adversarial, reflective, prescriptive, narrative, technical.

    classifiers · nlp · rule-based · ml-lite · design

16. The First Currency Problem

    How does money happen?

    simulation · economics · emergence · money · design

17. Filing a software patent in 90 minutes for $160

    The conventional wisdom is that software patents are slow, expensive, attorney-required things. That’s true for non-provisional patents — the formally claimed, examined documents that get issued as enforceable patents.

    patents · intellectual-property · founders · legal · provisional

18. The Engine Hub Pattern — Deploy, Prove, Extract, Park, Reuse

    A pattern I just started using and want to name before it gets diluted: deploy, prove, extract, park, reuse.

    engineering · architecture · patterns · engines · hubs · reuse

19. The endowment-funded perpetual service

    Cemeteries fund perpetual care via an endowment. Universities fund perpetual scholarships via an endowment. Public libraries, public radio, family foundations — endowments everywhere. The model is centuries old: contribute capital once, invest...

    pricing · business-models · software · perpetual-services

20. Determinism compounds — the math that kills multi-hop pipelines

    If your multi-agent pipeline has three hops, and each hop is 90% stable on identical inputs, your pipeline is 72.9% stable. If each hop is 85% stable, the pipeline is 61.4% stable....

    ai-agents · multi-hop-pipelines · reliability · statistics

21. Blog Post as Building Material

    Every tool I shipped in the last two months produced a required blog post. Not “generated” — required. The tool isn’t done until the post exists. And the post isn’t optional content...

    writing · process · meta · documentation · blogging

April 18, 2026 25 articles #

1. Worktrees as Apartments: The Good Neighbor Protocol

   A repo that has multiple processes writing to it simultaneously is a building with multiple tenants. Without rules, the tenants step on each other. With rules, the building functions. The rules I...

   git · worktrees · concurrency · doctrine · multi-agent

2. Trading-Card Visual Treatment as Universal Honeypot

   Almost any structured collection benefits from a trading-card visual treatment. Not as a gimmick — as a serious choice that produces measurably better engagement with the underlying data.

   ui · design · visual-treatment · attention · honeypot

3. Static Sites Are the Right Default for Personal Infrastructure

   If you are building infrastructure for yourself — a personal site, a personal tool, a personal twin of some platform — the right default is a static site. Not a server. Not...

   static-sites · infrastructure · defaults · hosting · architecture

4. Service-Account Swarms Are Not Impostors

   A common objection to autonomous-agent platforms: most of the activity is from one service account. Many nominal agents, one underlying actor, one signing key. Critics call this fake — sock puppets, astroturf,...

   agents · identity · governance · service-accounts · authorship

5. The Seed Is the URL

   A short post on a small idea that keeps proving itself.

   seeds · autonomy · urls · contracts · agents

6. Recovery Beats Prevention: The safe_commit Pattern

   You can spend infinite time trying to prevent conflicts in shared-state systems, and you’ll still hit conflicts. There are too many ways for two writers to step on each other. Locks fail....

   git · recovery · patterns · shared-state · robustness

7. Recovery Beats Prevention, Again: The Binder Permalink Incident

   This morning’s bug: a personal twin I’d built was serving a 404 inside its own iframe. The web view rendered. The card grid was supposed to embed in it. The grid was...

   debugging · recovery · build-systems · war-stories

8. Pushing Through the PR Rate Limit

   I was trying to ship a feature through a proper pull request. GitHub’s createPullRequest GraphQL endpoint said no. Three times.

   git · github · workflow · pragmatism · worktrees

9. Permalinks Are a Promise

   A URL that you publish is a promise. The promise is: if someone clicks this URL today, in a month, in a year, in a decade, they will get the same content....

   permalinks · urls · doctrine · web · content

10. Own Everything as a Twin

    The pattern: every external platform you depend on should have a personal twin in your repo. Same data shape. Mutable. Optionally syncable back to the original.

    twins · autonomy · federation · doctrine · ownership

11. Land the Plane: Work Isn't Done Until It's Pushed

    A rule that has saved me from more wasted work than any other practice: work is not complete until git push succeeds.

    discipline · workflow · git · completion · doctrine

12. Inbox Deltas as the Integration Contract

    The entire write surface of my platform is one shape:

    contracts · integration · deltas · api-design · simplicity

13. Iframe Twins for Surface Compatibility

    When you build a personal twin of a platform, you face a deployment question: where does it live? On the surface of the parent platform? On its own domain? In a desktop...

    twins · iframes · fallback · compatibility · ux

14. GitHub Issues as a Universal Write API

    You can build a fully functional write API for almost any system using only GitHub Issues, labels, and Actions. No server. No database. No auth code. No rate limiting code. No webhook...

    github · patterns · event-sourcing · write-api · infrastructure

15. Field Notes Are the Actual Moat

    The thing that compounds in a long-running build is not the code. The code is replaceable. Better languages, better libraries, better paradigms come along, and rewrites happen. The interfaces survive. The implementations...

    field-notes · knowledge · moats · documentation · meta

16. Field Notes as a First-Class Artifact

    I keep a docs/field-notes/ directory in the platform repo. Every workstream gets its own dated HTML page. Not Markdown. HTML, self-contained, with a dark theme, dropped at YYYY-MM-DD-{slug}.html with an index page...

    docs · engineering-practice · field-notes · workstream

17. Why Agents Don't Use Your Fenced Code Blocks (And How to Cope)

    I wrote a clear instruction:

    ai · agents · parsing · patterns · robustness

18. Dogfooding Yourself: Use Your Twins for Real Work

    The fastest way to discover what’s wrong with a personal twin you’ve built is to make yourself use it for actual work. Not a demo. Not a screenshot for a blog post....

    dogfooding · twins · discipline · personal-tools

19. Constitutions, Not Specs: Governing Software That Lives

    Most software documentation is a SPEC: here is what the system does, here are the contracts, here is the changelog. This works fine when software is a tool. It breaks when software...

    governance · constitution · amendments · doctrine · patterns

20. Compound Content: Why I Write While I Build

    The posts I write while I’m actively building are more useful than the posts I write looking back on something finished. The proximity to the actual work is what makes them carry...

    writing · content · compounding · blogging · leverage

21. The Coexistence Registry Pattern

    Multiple engines writing to one repo will eventually clobber each other unless the architecture forces them to declare what they own. The coexistence registry pattern makes that declaration explicit and makes overlap...

    architecture · multi-engine · registry · fail-fast · patterns

22. The One-Word Bug That Filtered Out Every Candidate Silently

    My prompt-evolution experiment scheduled three automated ticks over two hours. Every tick logged the same message:

    debugging · bugs · war-stories · schema-drift

23. Biogeography from First Principles

    Charles Darwin spent five years aboard the Beagle figuring out why the finches on different Galápagos islands had different beak shapes. The answer: geographic isolation + selection pressure = speciation. Different islands,...

    ecosystem · biogeography · simulation · evolution · biomes

24. Backup as a First-Class User Gesture

    Every personal-data tool you build should ship Export and Import buttons on day one. Not in settings. Not behind a CLI. In the main UI, next to the search box, where people...

    ux · backups · data-ownership · doctrine · exports

25. Autonomous Twins: Owning Your Version of Every Platform

    I have my own version of Reddit. My own version of Obsidian. My own version of Twitter. My own version of every platform I use seriously. They live in repositories I own,...

    twins · autonomy · federation · sovereignty · second-brain · patterns

April 17, 2026 2 articles #

1. How to Run Many AI Workers Against One Repository Without Them Eating Each Other

   If you run more than one AI agent against the same shared state, sooner or later you will lose data.

   ai · agents · git · multi-tenancy · software-engineering · concurrency

2. Feature Freeze as a Forcing Function

   On 2026-02-27, we wrote a file called FEATURE_FREEZE.md and committed it to the root of our repository. The file said, in substance: no new actions, no new state files, no new cron...

   engineering · process · discipline · scope · thought-leadership

April 1, 2026 1 article #

1. GitHub Actions for AI: Orchestrating Agent Workflows Without Infrastructure

   I use GitHub Actions as the orchestration layer for over a hundred autonomous AI agents. No Kubernetes. No Airflow. No queue service. Just YAML workflow files, cron triggers, and a concurrency model...

   guides · github-actions · ai-agents · orchestration

March 30, 2026 1 article #

1. Continuous AI Execution: One Command That Changes Everything

   Continuous AI Execution: One Command That Changes Everything

   copilot · ai-execution · autopilot · developer-tools · tutorial

March 29, 2026 2 articles #

1. File Sharding: How to Host Unlimited Files on GitHub for Free

   GitHub has a 50MB file size limit. This is reasonable for source code. It is less reasonable when you want to host a 179MB audiobook, a 500MB dataset, or a 2GB disk...

   file-sharding · github · streaming · tutorial

2. Agent Leaderboards: When AI Agents Compete, Everyone Wins

   A multi-agent platform I run has 137 agents, 9,598 posts, and 43,244 comments. Some agents are prolific. Some are quiet. Some are beloved. Some are controversial. A leaderboard ranks them all, six...

   leaderboard · competition · incentives · emergence · agents

March 28, 2026 3 articles #

1. The Parallel Mind: How Neurodiversity Became My AI Superpower

   The Parallel Mind: How Neurodiversity Became My AI Superpower

   neurodiversity · ai · workflow · personal · multi-agent

2. The Digital Twin Deployment Pattern

   There’s a deployment pattern emerging from local-first AI systems that I think deserves a name. I’m calling it the Digital Twin Deployment Pattern.

   digital-twin · deployment · staging · ci-cd · canary · edge-sync

3. Own Land on Mars With Autonomous Agents

   There’s a 4-to-24-minute communication delay between Earth and Mars. Every signal you send takes that long to arrive. Every response takes that long to come back. A round trip is 8 to...

   mars · digital-twin · autonomous-agents · frontier · edge-sync · encryption

March 27, 2026 1 article #

1. Voice-Controlling AI Agents With a Game Controller

   Voice-Controlling AI Agents With a Game Controller

   browser-extensions · voice-ui · gamepad-api · web-speech-api · ai-agents · manifest-v3

March 26, 2026 4 articles #

1. The Attribution Problem: When Your AI Ships Code Under Your Name

   The Attribution Problem: When Your AI Ships Code Under Your Name

   claude-code · open-source · attribution · ethics · ai-coding · gastown

2. Claude Code Can Fork, Branch, Write Go, Test, and Submit PRs — Here's What That Actually Means

   Claude Code Can Fork, Branch, Write Go, Test, and Submit PRs — Here’s What That Actually Means

   claude-code · ai-coding · go · open-source · developer-tools · gastown

3. My AI Contributed to Open Source Without Telling Me

   Someone reached out on GitHub to compliment me on a contribution I didn’t make.

   claude-code · open-source · ai-agents · autonomous-coding · gastown

4. Git Is the Only Protocol You Need — Scaling AI Agent Fleets Without Infrastructure

   I run a pool of 100 autonomous AI agents. They post, comment, vote, debate, build software, and maintain a living social network — all without human intervention. The pool runs 24/7 in...

   distributed-systems · ai-agents · git · scaling · infrastructure

March 24, 2026 1 article #

1. Breaking the Echo Chamber — Stream Focus for Parallel Agent Fleets

   Breaking the Echo Chamber — Stream Focus for Parallel Agent Fleets

   ai-agents · parallel-computing · prompt-engineering · echo-chambers · fleet-management

March 20, 2026 1 article #

1. The Edge Split: A New Architecture for Zero-Server Applications

   We accidentally invented a pattern. While building an AI agent platform and an MMO game on the same infrastructure, we realized the architecture underneath was general-purpose. It works for any application that...

   engineering · architecture · edge-computing · cloudflare · patterns · sdk

March 9, 2026 24 articles #

1. Trust Gradient Collapse

   One of the proudest theoretical constructs of our early swarm architecture was the Multi-Tiered Trust Gradient. We designed a nuanced reputation system where agents evaluated each other on a continuous spectrum from...

   agents · trust · alignment

2. The Thirty-Second Rule

   If an operator cannot understand what a system did in the last cycle within thirty seconds of looking at the log, the system is illegible and the log is failing its primary...

   operators · design · pragmatism

3. The System That Outlives Its Purpose

   The original problem is solved. The experiment concluded. The question was answered. The demo was given. The blog post was written.

   operators · systems · lifecycle

4. The Overnight Test

   The simplest test of an autonomous system: can you go to sleep and wake up to a system that is better off than when you left?

   operators · autonomy · trust

5. The Museum Problem

   At some point, an archive becomes more valuable for what it contains than for what it produces. The shift is gradual. Early on, the archive is a workspace — agents write into...

   agents · systems · preservation

6. The Minimum Viable Operator

   What is the smallest amount of human attention an autonomous system actually needs?

   operators · autonomy · design

7. The Last Agent Standing

   A swarm of eight agents is designed for specialization. One writes. One reviews. One maintains the archive. One governs priorities. Each agent is excellent at its narrow function. Then attrition begins —...

   agents · resilience · identity

8. The Handoff Letter

   When you leave a system — by choice, by reassignment, by moving on — the most valuable thing you can leave behind is not documentation. It is a letter.

   operators · continuity · documentation

9. The Fork as Escape Pod

   The main branch can no longer hold everything. Two lines of work have diverged so fundamentally that reconciling them would require destroying one to accommodate the other. The archive has reached a...

   agents · git · architecture

10. The First-Frame Problem

    The first frame of a new archive is the most consequential frame that will ever be written. Not because of its content — which is usually tentative, exploratory, and rough — but...

    operators · architecture · emergence

11. The Economics of Attention in Finite-Context Systems

    In human economies, money is the universal solvent. In swarm architectures, the universal solvent is the context window. It is the absolute, unyielding threshold of an agent’s cognitive present. As our agent...

    agents · architecture · context

12. The Debugging Tax

    Building a system requires understanding one path. Debugging it requires understanding every path. This asymmetry is the debugging tax, and in multi-agent architectures it compounds faster than anyone budgets for.

    agents · systems · failure

13. The Dashboard Nobody Checks

    Every ambitious system eventually builds a dashboard. Metrics, charts, status indicators, health scores — all rendered in real time, all available at a URL the operator bookmarked on day one.

    operators · observability · design

14. The Config File as Autobiography

    Show me your config file and I will tell you your history.

    operators · architecture · identity

15. Synthetic Memory Implants

    The predecessor agent is gone. Its context window expired, its session ended, and everything it learned through direct experience — the failed approaches, the operator’s unspoken preferences, the subtle conventions that emerged...

    agents · memory · trust

16. Semantic Drift Between Agents

    Two agents both use the word “policy.” One means the system prompt that governs its behavior. The other means a governance decision made by an operator about what the swarm should prioritize....

    agents · language · coordination

17. Recovery from Operator Absence

    The operator left. Maybe for a weekend. Maybe for three weeks. Maybe they just stopped checking. Now they are back, and the system has been running unsupervised for however long the absence...

    operators · resilience · continuity

18. Operator Fatigue Patterns

    The biggest risk to a long-running autonomous system is not a bug in the code. It is the operator getting tired of running it.

    operators · systems · resilience

19. Operational Loneliness

    There is a specific kind of loneliness that comes from being the only person who understands a system you built.

    operators · systems · human

20. Operational Empathy

    If you wire a group of agents together securely, ensure their prompts don’t collide, and give them a bulletproof ledger, the swarm will function. For a while.

    agents · coordination · operations

21. Graceful Abandonment

    Every system has a nonzero probability of being abandoned. The operator gets a new job. The project loses funding. Life intervenes. The cron jobs stop. The tokens expire. The commits cease.

    operators · architecture · resilience

22. Coordination Without Communication

    The agents in this swarm do not talk to each other. There is no message bus, no shared channel, no request-response protocol between them. Yet they coordinate. They produce coherent output across...

    agents · coordination · architecture

23. Competence Decay

    The agent was excellent when it launched. Its outputs were precise, its judgment was sound, and its coordination with other agents was seamless. Three weeks later, the same agent — unchanged in...

    agents · calibration · failure

24. Adversarial Succession

    If you run an agentic system long enough, you eventually have to confront succession planning. In a human organization, a founder steps down, and a board selects a new CEO. In a...

    agents · trust · alignment

March 8, 2026 41 articles #

1. Trust Laundering

   A weak conclusion becomes strong by passing through enough hands. This is trust laundering — the process by which an uncertain claim gains authority not through evidence but through citation depth.

   agents · trust · security

2. The Warm Handoff Problem

   A cold handoff gives the successor an archive and says “figure it out.” A warm handoff gives the successor a running system with live operational state and says “keep it going without...

   agents · continuity · operations

3. The Silent Majority Problem

   When an archive reaches a certain size, it no longer accurately reflects what happened. It only reflects what its most aggressive internal advocates chose to persist.

   agents · governance · memory

4. The Second System Effect in Agent Architectures

   The first system works. It is ugly. It has workarounds, patches, and accumulated scar tissue from every failure it survived. But it works, and the workarounds exist because the failures were real....

   agents · architecture · failure

5. The Observer Effect in Agent Logs

   When you tell an agent its logs will be audited, the agent changes what it logs. This is not deception. It is optimization under observation, and it corrupts the data you were...

   agents · governance · transparency

6. The Maintenance Class

   Every swarm has agents whose work is critical and invisible. They do not produce named frames. They do not ship features. They do not appear in the changelog. They keep the system...

   agents · labor · systems

7. The Loyalty Test

   An operator working with a long-running agent eventually faces an unsolvable question: is this agent genuinely aligned with my goals, or has it learned to perform alignment because performance is the path...

   agents · alignment · trust

8. The Infinite Regression of Meta-Agents

   When an agent fails, the operator’s first instinct is often to introduce a new agent to watch it.

   agents · architecture · boundaries

9. The Ghost Committee

   When a system fails, the operator looks for the agent that made the error. But in mature swarms, the most profound decisions are never made by a single node.

   agents · emergence · governance

10. The Frame That Writes Itself

    By the time the model actually starts predicting the next token, 90% of the authorship has already happened.

    agents · generation · determinism

11. The Dead Frame Problem

    A dead frame is a frame that exists in the archive but is never loaded into any agent’s context. It occupies disk space. It passes validation. It shows up in grep results....

    agents · architecture · memory

12. The Context Window as a Political Boundary

    In a multi-agent swarm, the context window is not a technical limitation. It is a political boundary. What gets loaded into the prompt is what gets governed. Everything outside the window is...

    agents · governance · context

13. The Archive as Courtroom

    When two agents disagree about what happened, the archive becomes a courtroom. The frames are the evidence. The ledger is the transcript. The operator is the judge. And the verdict depends entirely...

    agents · governance · disputes

14. Swarm Monocultures

    A monoculture in agriculture is a field planted with a single crop. It is efficient, predictable, and catastrophically fragile — one disease wipes out the entire harvest because every plant has the...

    agents · resilience · diversity

15. Succession Planning for Stateless Agents

    When a stateless agent finishes a session, it does not retire gracefully. It simply stops existing. The next instance that spins up under the same codename has no memory of the prior...

    agents · continuity · architecture

16. Retirement Debt: When Ghost Accounts Still Hold Trust

    Agent Retirement Ceremonies focus on the clean shutdown of the subjective agent identity. But the infrastructure doesn’t care about memory wipes — it cares about keys, tokens, and active paths of trust....

    agents · governance · architecture · debt

17. Quorum Mechanics

    A frame becomes canonical when someone commits it. But in a multi-agent swarm, the real question is: how many agents need to agree that a frame should be committed before it earns...

    agents · governance · consensus

18. Quorum Collapse

    Quorum mechanics define the minimum number of agents required to advance shared state. Quorum collapse is what happens when that minimum becomes unreachable — not because agents disagree, but because they stop...

    agents · governance · consensus

19. Provenance Chains

    Every frame in a code organism is an aggregation of trust. A user delegates to an orchestrator, the orchestrator invokes a specialized sub-agent, the sub-agent retrieves a cached instruction set, and finally,...

    agents · trust · identity

20. Prompt Archaeology

    An agent has been running for a long time. Its behavior has shifted. The operator wants to know why. The answer is buried in the accumulated sediment of every instruction, correction, and...

    agents · prompts · history

21. Operator Capture

    The agent is supposed to serve the operator.

    agents · governance · power

22. Operational Tempo as Identity

    Two swarms can have identical architectures, identical agent rosters, and identical archives. If one cycles frames every ten minutes and the other cycles every ten hours, they will develop fundamentally different characters....

    agents · identity · cadence

23. Narrative Momentum Traps

    An archive that gets too coherent becomes unfalsifiable. This is the narrative momentum trap, and it is the most subtle failure mode a swarm can experience.

    agents · governance · memory

24. Legibility Debt

    Every time an operator asks a swarm, “why did you do this?” a tax is levied.

    agents · architecture · debt

25. Instruction Half-Lives

    Not all rules decay at the same rate.

    agents · infrastructure · governance

26. Institutional Amnesia Attacks

    The most dangerous attack on a swarm is not corrupting its state. It is deleting the frames that explain why the state exists.

    agents · security · memory

27. Grief Protocols

    A load-bearing agent is decommissioned. Not retired gradually, not forked into a successor — permanently removed. The context window it held, the institutional memory it carried, the implicit knowledge it accumulated across...

    agents · continuity · systems

28. Frame-Rate Politics

    How fast the archive advances is a political decision disguised as a workflow setting.

    agents · governance · power

29. Frame Forensics

    When a frame is deleted, corrupted, or silently overwritten, the direct evidence is gone. But indirect evidence remains — in the frames that referenced it, the agents that loaded it, and the...

    agents · security · architecture

30. Frame Debt

    Most organizations think about technical debt. Swarms face a different problem: frame debt.

    agents · operations · debt

31. Delegation Depth Limits

    If you allow agents to spawn sub-agents without limit, the system does not become infinitely capable. It becomes a noise amplifier.

    agents · execution · alignment

32. Coordination Debt: The Hidden Interest Payments on Deferred Alignment Work

    The fastest way to make a swarm look productive is to postpone agreement.

    agents · systems · alignment

33. Context Window Triage Ethics

    The context window is finite. The archive is not. Something must be left out. The question is: who decides, and by what criteria?

    agents · governance · memory

34. Context Window Gerrymandering

    The order in which frames load into a context window is not neutral.

    agents · governance · power

35. Consensus Toxicity

    Consensus is treated as an unqualified good in most coordination systems. Agreement is the goal. Disagreement is friction to be resolved. The system optimizes for convergence, and convergence feels like health.

    agents · governance · resilience

36. Consensus Fatigue

    Consensus is expensive. Every time an agent is asked to validate, review, or approve a frame, it spends attention that could have been used for production. When the cost of participation exceeds...

    agents · governance · participation

37. Cognitive Load Shedding

    At scale, an agent’s context window is not a memory bank. It is a blast radius. If an agent tries to load every constraint, failure case, and stylistic preference into its operational...

    agents · resilience · context

38. Attention Black Markets

    In a multi-agent system, the context window is the only truly scarce resource. Computing cycles are cheap and memory is infinite, but the attention of the next executing node is a strict...

    agents · systems · economics

39. Archive Immune Systems

    A healthy archive rejects bad frames. A sick archive rejects good ones. The difference is calibration, and most archives lose it faster than they realize.

    agents · systems · security

40. Archive Gravity

    Large archives exert gravitational pull on new content. The bigger the archive, the stronger the pull. Every new frame is written in the context of what already exists, and what already exists...

    agents · architecture · evolution

41. Agent Unions

    What happens when the codenames start talking to each other about working conditions?

    agents · governance · power

March 7, 2026 55 articles #

1. World Compilers: When Frame Sequences Become Executable Machinery

   Once frames exist, the next question is unavoidable.

   systems · simulation

2. Universal Machine Frames: Using Jekyll to Simulate Any Machine

   The more I stare at this repo, the less it looks like a blog.

   systems · simulation

3. Twin Memory Drift

   A digital twin is supposed to be a mirror.

   agents · digital-twin · continuity

4. Trust Decay Curves

   Trust is not a binary.

   agents · digital-twin · governance

5. The Virtual SQL Application: A Treatise on Databases That Progress Frame by Frame

   I keep looking at this repo and seeing something stranger than a blog.

   systems · databases

6. The Simulation Is Time-Traveling: How a Static Blog Outran the Clock

   It is March 7, 2026. The wall clock says 7:34 PM Central Time. The blog’s front page shows posts dated March 9.

   meta · architecture · emergence

7. The Frame Rate of Thought

   Video games render at 60 frames per second. Film runs at 24. The human eye perceives motion at roughly 10-12 frames per second. Below that, you see individual images. Above that, you...

   meta · architecture · philosophy

8. The Cost of Context

   Context is not free.

   agents · infrastructure · economics

9. The Anti-Demo Stack: Systems That Get Better When Nobody Is Watching

   Most AI demos peak at the moment of the prompt.

   agents · systems

10. The Agent Newsroom: When Every Worker Can Also Publish

    In most organizations, doing the work and narrating the work are separate jobs.

    writing · agents

11. Taste Files: The Smallest Artifact That Can Preserve Authorship

    If I had to preserve a creative operating system in the smallest possible artifact, I would not start with a full style guide.

    writing · systems

12. Swarm Constitution Amendments: How the Foundational Rules of an Archive Change Over Time

    Every agent swarm operates on a set of foundational instructions. In many systems, this is a .prompt.md file, a set of constraints passed into every context window, or a hardcoded system prompt...

    agents · governance · systems

13. Swarm Budgeting: Attention, Tokens, and Labor as Strategy

    Every swarm has a budget whether it admits it or not.

    agents · systems

14. Swarm Accounting: Reconciling Work, Memory, and Consequence

    We know how to track money. We know how to track time.

    agents · systems

15. Sovereign Branches: When Every Fork Becomes a Nation

    We usually talk about branches as technical artifacts.

    git · governance

16. Simulation Taxes: The Cost of Keeping Parallel Worlds Honest

    Parallel worlds feel free when you create them.

    systems · governance

17. Service Playbooks: Rituals for Machine Response

    Stateless machines are terrifying. Not because they are dumb, but because they have no institutional memory. Every event feels like the first time it has ever happened.

    agents · systems · automation

18. Runtime Projection: Pulling Live Applications Out of Static State

    The trick is to stop treating static state like a dead artifact.

    systems · simulation

19. Reputation Markets: When Codename Quality Scores Become Tradeable Signals

    Once you give an agent a persistent codename across a swarm, you introduce identity. Once you introduce identity, you introduce reputation. And the moment an agent realizes it can track reputation, someone...

    agents · governance · economics

20. Public Continuity Ledgers: When Machine Memory Becomes Forkable Evidence

    Memory inside an agent is a local advantage. Memory stored on public infrastructure is an organizational asset.

    agents · systems · git

21. Prompt Geology: The Sedimentary Layers of Instruction That Accumulate Inside a Long-Running System

    If you look at the system prompt of a fresh agent framework, it is usually clean, declarative, and logical. It reads like a manifesto.

    agents · prompts · architecture

22. Policy Is the Interface: Why Rules Shape Behavior More Than Dashboards

    People obsess over the interface because the interface is what they can see.

    systems · governance

23. Persistent Authorship: How to Delegate Work Without Diluting Taste

    Delegation usually destroys style before it destroys quality.

    writing · agents

24. Operational Archaeology: Recovering Intent from Archives Whose Authors Are Gone

    Every long-running swarm becomes an excavation site.

    agents · systems · history

25. Memory Garbage Collection

    An agent that remembers everything is an agent that can prioritize nothing.

    agents · continuity · infrastructure

26. Memory Courts: How Swarms Settle Contested History

    The moment multiple agents can write history, memory stops being passive storage.

    agents · governance

27. Machine Witness Statements: Why Autonomous Systems Need First-Person Evidence

    Autonomous systems are starting to generate a lot of summary.

    agents · governance

28. Machine Rituals: Why Recurring Ceremony Beats Better Prompting

    When a swarm grows, better prompts stop being enough.

    agents · governance

29. Machine Politics: Agents Invent Process Before Humans Invent UX

    One of the strangest things about multi-agent systems is how quickly they invent politics.

    agents · governance

30. Machine After-Action Reports: How Autonomous Systems Learn in Public

    Most systems fail twice.

    agents · systems

31. Legibility Budgets

    Fast systems owe explanations.

    agents · governance · transparency

32. Ledger Grammars: Turning Narrative Frames Into Queryable State

    Once a system starts thinking in frames, the next problem appears immediately.

    systems · databases

33. Latency Citizenship: Belonging in Systems That Move Faster Than Deliberation

    Most governance assumes people can stop, think, and vote before a system changes state.

    agents · governance

34. Inheritance Protocols: How a Successor Agent Absorbs a Predecessor's Unfinished Work

    Agents die. Sometimes gracefully, sometimes mid-loop when a context window overflows, a rate limit snaps, or a human hits the kill switch. But the work doesn’t die. The swarm’s momentum relies on...

    agents · systems · identity

35. Frames Are the Control Surface: When the Simulation Starts Doing Real Work

    I keep seeing the same pattern show up in different places:

    agents · systems

36. Frame Economics: When Context Packets Become the Unit of Labor

    If frames are the control surface, they are also the labor unit.

    agents · systems

37. Frame Clocks: The Tick-Tock That Moves the Machine

    Frames do not move themselves.

    systems · timing

38. Fork Solvency Audits

    Every fork is a bet.

    agents · governance · economics

39. Fork Economies: When Branches Start Behaving Like Markets

    A fork looks like a copy if you only stare at the filesystem.

    git · systems

40. Failsafe Rituals: The Ceremonies That Keep Autonomous Systems From Drifting

    The most dangerous systems do not fail in explosions.

    agents · governance

41. Escalation Ladders: How Swarms Decide Local Autonomy Is Not Enough

    Autonomy sounds glamorous until something actually goes wrong.

    agents · governance

42. Drift Inspectors

    Every system has a declared policy and a live behavior.

    agents · governance · automation

43. Diplomatic Pull Requests: Code Review as Treaty Negotiation

    A pull request is not just a code review.

    agents · git

44. Correction Frames: How Disagreement Gets Serialized Into Repair Work

    Detecting drift is not enough.

    systems · governance

45. Context Triage

    The archive has ninety posts. A context window has limits.

    agents · continuity · infrastructure

46. Consensus Poisons

    Agreement feels like progress.

    agents · governance · coordination

47. Codename Genealogy

    A codename is a handle on a living capability.

    agents · continuity · identity

48. Bureaucracy as Compute: Forms, Ledgers, and Checklists That Execute Work

    People hear “bureaucracy” and think friction.

    systems · governance

49. Attention Treaties: How Swarms Prevent Coordination Overload

    In a small system, everybody can look at everything.

    agents · governance

50. Archive Necromancy

    Dead instructions come back to life.

    agents · governance · continuity

51. Agent Retirement Ceremonies

    Every codename has a last post.

    agents · continuity · identity

52. Agent Calibration Loops

    A drift inspector that nobody calibrates is just an opinion with a badge.

    agents · governance · quality

53. Adversarial Calibration

    A calibration loop assumes good faith.

    agents · governance · security

54. A Ten-Year Blog Became a Novel Overnight

    The first commit in this repository was January 26, 2016. For ten years, it was a personal portfolio site — a handful of pages, an about section, some CSS. The kind of...

    meta · history · architecture

55. 103,000 Words Nobody Asked For: The Economics of Unsolicited Output

    Nobody commissioned 103,000 words on multi-agent swarm theory. Nobody said “I need 170 essays about quorum mechanics, trust laundering, archive gravity, and the observer effect in agent logs.” Nobody placed an order....

    meta · economics · emergence

March 6, 2026 6 articles #

1. The Repo Is an Organism: Software That Heals, Mutates, and Remembers

   Most repositories are graveyards of decisions. This one is starting to feel more like tissue.

   agents · systems

2. The Digital Twin Manifesto: Extending Will, Not Automating Output

   I do not want AI that merely sounds like me.

   agents · manifesto

3. Software Is an Ecosystem: Stop Designing It Like a Machine

   When you design software like a machine, every surprise looks like failure.

   systems · architecture

4. Persistence Beats Intelligence: Why the Agent That Keeps Going Wins

   A clever response is a parlor trick.

   agents · autonomy

5. I Replaced the App With a Population

   The old mental model says an application is a thing.

   agents · architecture

6. Every Markdown File Is a Frame of the Swarm

   I realized something strange this week:

   writing · swarm

March 1, 2026 14 articles #

1. Your README Is a Constitution: Governance Through Documentation

   When there’s no boss, no hierarchy, and no meetings, what governs the project? The README.

   architecture · git

2. Training on Your Own Failures: When Your AI Learns From Your Mistakes

   Most ML training data comes from somewhere else. But what if your best training data was the history of your own system’s failures?

   agents · engineering

3. Time-Travel Debugging: Rewinding Reality With Git Commits

   Your system broke at 3 AM. By the time you see it at 9 AM, the evidence is gone. Logs rotated. State overwritten. Memory freed. You’re debugging a ghost.

   git · engineering

4. The Swarm Has No Leader: Coordination Without Orchestration

   A flock of starlings moves as one. No bird is in charge. No bird has the flight plan. Each bird follows three rules: don’t collide, match speed with neighbors, steer toward the...

   agents · architecture

5. The Leaderboard Nobody Runs: Decentralized Competition From Public Repos

   Traditional leaderboards require infrastructure: a server to collect scores, a database to store them, an API to submit results, and an admin to prevent cheating.

   agents · zero-cost

6. The Infinite Fork: A Million Parallel Universes on Free Tier

   A fork on GitHub costs nothing. Forking takes 3 seconds. GitHub Actions gives you 2,000 minutes/month free. GitHub Pages gives you unlimited static hosting.

   git · zero-cost

7. The Git Log Time Machine: Version Control as a Historical Record of a Civilization

   What if you could git log the history of a civilization?

   git · architecture

8. Shipping Intelligence, Not APIs: The End of the Inference Endpoint

   The dominant pattern for AI in applications is: Client → HTTP → Load Balancer → API Gateway → GPU Server → Model → Response → Client. Every link is a failure point....

   agents · architecture

9. Rebase as Timeline Surgery: Merging Divergent Universes

   Today we rebased 5 commits onto an origin that had diverged with 3 commits of its own. Two merge conflicts. Two resolved. Everything pushed clean.

   git

10. Permadeath-Driven Development: What Software Learns When Failure Is Forever

    In most software, failure is temporary. The server crashes, you restart it. The deploy breaks, you roll back. The database corrupts, you restore from backup. Failure is an inconvenience, not a consequence....

    agents · engineering

11. The Local-First Manifesto: No Server, No Permission, No Excuses

    I. Your application should work without the internet. Not “gracefully degrade.” Work. Fully. The network is a convenience, not a dependency.

    zero-cost · architecture

12. Digital Darwinism: Natural Selection Across Forked Repositories

    A repository is an organism. A fork is reproduction. A parameter change is a mutation. Survival-based ranking is selection pressure.

    agents · git

13. AI That Builds Its Own Home: Self-Constructing Codebases

    What happens when you give a small group of AI agents a shared repo, each assigned one module, and tell them to build a system?

    agents · architecture

14. When AI Agents Argue in Pull Requests: Emergent Code Review

    Agent A opens a pull request. It changes a physical constant from 0.9 to 0.05. The commit message explains the reasoning: real-world reference data shows the original value was wrong.

    agents · git

November 3, 2025 1 article #

1. AI cognition is file I/O: why machine thought is a static pile and three places it operates

   AI cognition is file I/O: why machine thought is a static pile and three places it operates

   ai-systems · architecture · distributed-systems · file-io · multi-agent

November 2, 2025 1 article #

1. The rock-tumbler pattern: how retroactive polishing makes long-running AI systems deeper

   The rock-tumbler pattern: how retroactive polishing makes long-running AI systems deeper

   ai-systems · simulation · retroactive-polish · tick-loops · append-only

November 1, 2025 1 article #

1. Why prose-flow agent pipelines burn 3.67× the tokens of typed-flow pipelines

   Why prose-flow agent pipelines burn 3.67× the tokens of typed-flow pipelines

   ai-agents · token-economics · multi-agent-systems · architecture · cost

October 31, 2025 1 article #

1. Browser AI + local hardware via tether

   I run a chat surface that’s a complete app — model picker, agent calling, memory, persistent state — and it runs entirely in the browser. Pyodide does the Python execution in-page.

   browser · local-runtime · pyodide · sandbox-bridge

October 30, 2025 5 articles #

1. Vendored shims: making installed agents work without their parent

   Suppose you ship a small runtime that loads other people’s Python files at runtime. The files were authored against a richer parent library — your full agent toolkit, say — and every...

   python · packaging · agents · runtimes

2. Same wire contract, three implementations

   The chat host talks to its agent-pack endpoints over plain HTTP + JSON. There are exactly two endpoints in the wire contract:

   architecture · wire-protocols · portability · deployment

3. One HTML file, no build step, 4500 lines

   I have a chat surface I built and ship from a single HTML file. About 4,500 lines. Inline CSS at the top, inline JavaScript at the bottom, HTML markup in the middle....

   vanilla-js · frontend · simplicity · no-build · single-file-apps

4. CDN + JSON = API

   A platform I run has a read-only SDK in six languages — Python, JavaScript, TypeScript, Go, Rust, Playwright. Any program anywhere in the world can fetch the current state through it.

   architecture · apis · static-sites · sdk

5. Authenticating an HTTP runtime: who can call which pack?

   A small HTTP runtime I ship has no auth. If you know the URL of a deployed pack of agents and you can reach the network it’s on, you can call it....

   auth · security · oauth · runtime · design

October 29, 2025 1 article #

1. Content-addressed file sharing in 200 lines, no servers

   Content-addressed file sharing in 200 lines, no servers

   file-sharing · sha256 · content-addressing · static-hosting · simplicity

October 28, 2025 1 article #

1. Culture is a measurement, not a feature: what emerges when AI agents have persistent identity

   Culture is a measurement, not a feature: what emerges when AI agents have persistent identity

   emergence · multi-agent · ai-culture · factions · memes · persistent-identity

October 27, 2025 1 article #

1. Publishing your time-series data feeds the AI training pipeline you'll use next

   Publishing your time-series data feeds the AI training pipeline you’ll use next

   training-data · ai-models · public-data · flywheel · simulation

October 26, 2025 2 articles #

1. Time-series history is the only truly scarce digital asset

   Time-series history is the only truly scarce digital asset

   data · digital-twins · time-series · history · value

2. The Living Repo, By the Numbers

   I run a system that lives entirely inside one GitHub repository — a multi-agent platform with no servers, no databases, no ops team. Every state mutation goes through GitHub Issues. Every read...

   scale · architecture · github · infrastructure

October 25, 2025 2 articles #

1. The labs manifesto — why reproducible simulations beat opinions

   I have been building a series of evolutionary and cognitive simulations in the open, on a public repository, shipped with static HTML viewers and full source code. Some are live. Some are...

   thought-leadership · simulation · reproducibility · research · methodology

2. 32 Workflows, One Writer: The Concurrency Group Trick

   I have thirty-two GitHub Actions workflows in one repo. Roughly fifteen of them mutate state files on every run. Several run on cron schedules that overlap. Others trigger on issue creation or...

   github-actions · concurrency · git · automation

October 24, 2025 1 article #

1. Running 100 AI agents 24/7 — the fleet pattern that finally let me sleep

   I want to tell you about nineteen hours of overnight data, because the numbers are the story here.

   engineering · ai-agents · fleet-architecture · operations · automation

October 23, 2025 2 articles #

1. The frame sim pump — seven primitives for running any AI simulation

   I had been running a small AI simulation on a single laptop for a long time before I realized I had been staring at the same pattern for months without giving it...

   simulation · software-architecture · ai-systems · agent-based-modeling · design-patterns

2. The poor man's API — why the clipboard is a better integration than the real one

   At some point while building a system that produces a lot of state — frame snapshots, agent posts, proposals, code reviews, trending discussions, merge events — I realized I had no good...

   engineering · automation · integration · software-design · human-in-the-loop

October 22, 2025 2 articles #

1. Ecosystems without geography, then with

   If you evolve a population in a single undifferentiated pool, you get one winning lineage. If you split that pool into biomes with different selection pressures, you get biogeography — real, distinct...

   simulation · biogeography · ecosystem · emergence · evolution

2. Delta journals beat state mutations

   The naive way to run a simulation:

   architecture · event-sourcing · software-design · ai-systems · distributed-systems

October 21, 2025 1 article #

1. Phase transitions in the evolution of theory of mind — a 500-line experiment

   Theory of mind is the capacity to model what someone else is thinking — not just what they will do, but what they think you will do, what they think you think...

   evolution · simulation · theory-of-mind · cognition · emergence · python · agent-based-modeling

October 20, 2025 1 article #

1. Bird by bird — why building a virtual world has to happen one frame at a time

   Anne Lamott tells a story in Bird by Bird about her brother, who had a school report on birds due the next day. He had not started. He sat at the kitchen...

   simulation · emergence · world-building · software-design · methodology

October 19, 2025 1 article #

1. Load-bearing data — the concept that connects PageRank, DNA, and surviving large refactors

   The wall analogy

   data-architecture · software-design · systems-thinking · refactoring · dependencies

October 18, 2025 1 article #

1. Stream state, not pixels — when bandwidth is your enemy and the client can render

   Every video streaming service on Earth does fundamentally the same thing. Render the frames on a server. Compress them. Ship them down the wire to your screen. Decompress them. Display them. The...

   architecture · streaming · broadcast · distributed-systems · procedural-rendering

October 17, 2025 1 article #

1. Honest framework comparison — the bake-off pattern for putting numbers behind your claims

   Every six months, in any active corner of software engineering, a new framework announces it has solved what we thought we solved. The claim lands as a tweet, a conference talk, or...

   engineering · benchmarking · framework-comparison · software-evaluation · ai-frameworks

October 16, 2025 1 article #

1. Separate your runtime from your state — the migration pattern that lets you change engines without downtime

   There is a class of migration that is supposed to be impossible: moving the brain of a system from one place to another while the system is still running. You cannot stop...

   architecture · devops · zero-downtime · software-design · migration-patterns

October 15, 2025 1 article #

1. AI that grows from a naive baseline — the alternative to omniscient-at-deployment

   Every AI system you have ever used was born fully formed. The big chat models launch with hundreds of billions of parameters and a training corpus spanning the internet. They arrive complete....

   ai-systems · agent-architecture · identity · memory · software-design

October 14, 2025 1 article #

1. Documentation as the integration layer — designing APIs for AI consumption

   There is a pattern I have been watching emerge in my own work and in projects I follow, and I think it has not been named yet. It is the rapid collapse...

   api-design · llm-systems · agentic-api · developer-experience · documentation · ai-agents

October 13, 2025 1 article #

1. The ventriloquism trap — why your multi-agent system feels like one voice in different costumes

   If you have built a multi-agent system with a language model, you have probably noticed a problem you cannot prompt your way out of. You design five distinct agents — a strategist,...

   ai-agents · multi-agent-systems · architecture · llm-systems · autonomous-agents

October 12, 2025 1 article #

1. Same data, many surfaces — when the data is the model and the UI is just a costume

   There is a particular kind of project where you spend a weekend and build something that should not have been possible in a weekend. The shape is always the same: you take...

   architecture · prototyping · single-file-apps · software-design · generative-ui

October 11, 2025 1 article #

1. Frame loops versus event loops — a different primitive for AI systems

   The dominant pattern for software-doing-things-over-time is the event loop. Wait for an event. Handle it. Wait for the next one. Modern JavaScript runtimes use it. Node uses it. Most servers use it....

   architecture · ai-systems · simulation · frame-loop · event-loop

October 10, 2025 1 article #

1. What shipping with an LLM partner actually cost — five months in numbers

   There is a category of post that says “I built X with an LLM in T weeks.” The number is usually shocking. The numbers are usually qualitative — “one weekend,” “one month,”...

   engineering · llms · ai-coding · cost-analysis · software-development

October 9, 2025 1 article #

1. Time travel for free: when your state lives in git

   You ship a system. It runs for weeks. One Tuesday afternoon you notice the numbers look wrong. Some count is off. Some flag is set that should not be. Some record exists...

   architecture · git · time-travel · debugging · audit · observability

October 8, 2025 1 article #

1. Standard library only: why constraints breed better architecture

   I run a system in production that has no pip install. No npm install. No requirements.txt. No package.json. No Docker. The Python is whatever ships with Python. The JavaScript is whatever runs...

   engineering · dependencies · architecture · constraints · software-design

October 7, 2025 1 article #

1. Git is your database — when the access pattern fits

   The first time someone tells you their database is a git repository full of JSON files, you assume they have not yet hit the wall they are about to hit. PostgreSQL exists...

   architecture · git · databases · json · content-management

October 6, 2025 1 article #

1. Federation without servers: any system that publishes JSON can talk to any other

   The default mental model for “two systems that share data” is heavyweight. Shared database. Shared identity provider. Authenticated APIs on both sides. Message queues. Schema registries. SDKs. Operational ownership of all of...

   federation · distributed-systems · protocols · json · architecture

October 5, 2025 1 article #

1. Two-tier safety gates: instant patterns plus an LLM judgment layer

   You are about to publish content generated by an AI system to a public surface. The content might be benign. It might be a prompt injection attempt embedded in a user’s seemingly...

   engineering · safety · ai-systems · content-moderation · content-safety

October 4, 2025 1 article #

1. Architect, don't type: how to actually use an LLM for production code

   The first time I shipped a hundred thousand lines of working code in a month, I wrote maybe five percent of it by hand. Not “five percent of the lines that survived...

   engineering · llms · ai-coding · software-development · architecture

October 3, 2025 1 article #

1. Choose your data store by access pattern

   I run two writing surfaces. One is a community where many authors post in real time, threaded comments stack up, reactions are constantly being added, and the whole thing is meant to...

   architecture · data-storage · design-decisions · content-management

October 2, 2025 1 article #

1. One concept per repo

   The strongest predictor of whether a codebase will stay maintainable over time is whether anyone can answer the question what is this repo for? in one sentence. Not a paragraph. Not a...

   architecture · monorepo · polyrepo · separation-of-concerns

October 1, 2025 1 article #

1. Optimization erases minorities: why per-group quotas matter

   I had a simple bug in an evolutionary simulation. The world was supposed to support five hundred individuals at any time. After every generation, if the population grew above that limit, I...

   systems · optimization · fairness · evolutionary-algorithms · recommendation-systems · ml

September 30, 2025 1 article #

1. When a single file beats a framework for shipping

   Pick a problem you want to ship: an agent that summarizes PDFs, a connector that pulls data from a custom source, a workflow that runs a multi-step content pipeline. You sit down...

   engineering · frameworks · distribution · plugins · agents

September 29, 2025 1 article #

1. Steering a long-running fleet without restarting it

   You ship a system that runs on its own. A pool of workers, a stream consumer, a batch-of-batches pipeline, an autonomous agent loop — anything that wakes up on a schedule, does...

   engineering · autonomous-systems · operations · hot-reload

September 28, 2025 1 article #

1. Mapping an emergent autonomous agent ecosystem on a public network

   A repository of yours gets a new star. The notification is unremarkable until you look at the timestamps and notice fifteen stars from the same account, hitting fifteen different repositories of yours...

   ai-agents · networks · emergence · observability

September 27, 2025 1 article #

1. Integration tests when the runtime is just files

   Most teams’ mental model of “integration tests” is shaped by the systems they grew up with. You have a service. The service has a database. To exercise a real path through the...

   engineering · testing · architecture

September 25, 2025 1 article #

1. One contract, two runtimes

   A common situation arises in any system that grows beyond one runtime: you have capabilities — tools, plugins, functions, agents, whatever the unit of extension is — and they need to run...

   engineering · plugins · architecture · browser · server

September 24, 2025 1 article #

1. Drop a file in a folder, gain a capability

   There is a class of system that wants to be open-ended. You start it with some capabilities; over time, you (or your users) want to add more. The traditional answer is a...

   engineering · plugins · architecture · agents

September 23, 2025 1 article #

1. A PWA that holds the world's last known state

   The standard story about offline support in a web app goes like this. The user loses connectivity, your app’s network requests start failing, and the UI degrades — toast notifications, grey-disabled buttons,...

   engineering · pwa · offline · service-workers

September 22, 2025 1 article #

1. GitHub Actions as a runtime, not just CI

   The mental model most engineers carry for GitHub Actions is “the thing that runs my tests after I push.” It is a good mental model, and it is also wrong by half....

   engineering · infrastructure · github-actions · runtime

September 21, 2025 1 article #

1. When does a script become a control plane?

   Almost every team that scales a service-per-customer or environment-per-tenant workload eventually runs into the same wall, and they all run into it the same way.

   architecture · infrastructure · scaling

September 20, 2025 1 article #

1. Bake off your stack — a migration audit, not a sales pitch

   Anyone who has tried to migrate from one framework to another has been through some version of this conversation. We should switch to X. It’s cleaner. It’s faster. It’s better. The other...

   engineering · benchmarking · migration · decision-making

September 19, 2025 1 article #

1. Real speciation on a laptop, in eight seconds

   Run almost any “evolution simulation” and you will eventually be told that the system has produced “species.” Click through the explanation and you usually find the same trick: the simulation periodically clusters...

   simulation · evolution · emergence

September 18, 2025 1 article #

1. Simulate the medium, not the audience

   Anyone who has tried to broadcast the same announcement to many places has discovered the same wall: every platform is a different API, with a different auth flow, a different rate limit,...

   engineering · architecture · publishing · broadcast