The First Rule of The Foundry

“The first rule of Fight Club is you do not talk about Fight Club.” ~ Chuck Palahniuk, Fight Club

I am about to break the first rule, at length, in public, with a repository link at the bottom. In my defense, nobody in this particular club can be punched: the whole membership is made of software. Over the past few weeks I asked an AI to help me clean up this blog’s repository, and somewhere between deleting fifteen years of WordPress shrapnel and re-theming the site you’re currently squinting at, the thing quietly organized itself into a nine-member development team with defined roles, restricted permissions, and better work habits than I have ever personally demonstrated. So let me put my position on the table right here at the top: I’m releasing that team today, free, under MIT, and this post is the story of how it came to exist.

“You buy furniture. You tell yourself, this is the last sofa I will ever need in my life. Buy the sofa, then for a couple years you’re satisfied that no matter what goes wrong, at least you’ve got your sofa issue handled. Then the right set of dishes. Then the perfect bed. The drapes. The rug. Then you’re trapped in your lovely nest, and the things you used to own, now they own you.” ~ Chuck Palahniuk, Fight Club

Palahniuk was talking about a condo full of IKEA. I was living it with a CMS: every plugin another perfect set of dishes, every theme another rug, until the things my blog owned ended up owning my blog. Some blame is owed before any credit. A few months back, Tony Mattke over at routerjockey.com put the idea in my head that WordPress was a liability wearing a content-management costume, and that a static site generator like Hugo was the grown-up answer. He was right, and I migrated. What I did not appreciate at the time was that my migration would drag half of WordPress’s DNA along with it: seventeen thousand invisible soft hyphens jammed into the middle of ordinary words, eleven hundred decorative <span> tags, and a reading-time widget fossilized into the top of all 84 archived posts like a bug in amber. The site looked fine, mostly, if you didn’t copy any text, use a screen reader, or look closely. Which is to say it was broken in the way most shitty infrastructure is broken: quietly, comprehensively, and below the waterline.

This is where the bot army came in. I run my projects in parallel with Claude Code these days, and rather than have one giant model do everything in one sitting, I’d been building specialized subagents: one that only investigates, one that only plans, one that only writes code, one that only writes tests, and one whose entire personality is finding the mistakes the others made (sometimes, that’s a lot). Each is a small text file with a strict tool allowlist and a job description. The read-only agents literally cannot edit files; the reviewer cannot fix its own findings; the docs agent touches nothing but documentation. If that sounds less like the AI fever-dream spewed by AI-bros, and more like a well-run NOC with a change-control policy, congratulations: you get what this is, and you’re ahead of most of the marketing horse-shit on the subject.

The cleanup is what forged them into an actual team. The investigation agent found the mess; the implementer wrote a deterministic script to strip the cruft while leaving code blocks untouched; and the QA agent, given free rein and encouragement to distrust everyone, caught the one thing that would have genuinely hurt: the cleanup script had silently destroyed all 147 Markdown hard line breaks in the archive, which had reformatted a 130-line IOS boot log into a single run-on paragraph and done the same to a Robert Frost poem (don’t hate me, I’m a sucker for cliche at times). Two roads diverged in a yellow wood, and my tooling merged them into one lane without signaling. Humorously enough, with that near-miss, the same team that caught the bug also caused it. The lesson isn’t that the machines are infallible; it’s that an adversarial reviewer with permission to run the build catches what a well-meaning implementer cannot see. That was true of humans when I started my career, and it definitely survives contact with the future entirely intact.

Somewhere in all this, the team acquired a name, The Foundry, and I acquired the sort of misplaced pride normally reserved for a kid’s sports trophy. They re-themed the site while they were at it: the dark terminal look you’re seeing now, the phosphor-green accents, the little cursor that blinks when your mouse hovers on a link, the post titles that type themselves out like a modem-era login banner. I rejected exactly one proposal: a Matrix-style falling-code animation behind the homepage, on the grounds that I am trying to run a blog, not a screensaver from 1999. The team took the note gracefully, which is more than I can say for myself in most design reviews I’ve attended.

A word on standing, since I’m handing out affiliations today: I am a proud founding member of the Flat Network Society , an organization whose gravitas can be measured by the fact that “founding member” involved approximately one conversation and zero bylaws. It is less a professional body than a running joke with a domain name, which frankly describes half the institutions I’ve paid dues to, minus the honesty. I mention it partly because I find it hilarious, and partly because the Foundry operates on the same principle the Society does: small crew, clear opinions, no middle management bungling shit up like shit-flinging circus monkeys.

So here’s the release. The whole team lives at github.com/SomeClown/the-foundry : nine agent definitions in plain Markdown, the pipeline that sequences them, the permission model, and a README explaining how to install them into your own Claude Code setup in about ninety seconds. MIT licensed, so do what you like. The honest caveats are in the README too: the agent-teams mode is experimental, the model assignments cost real money at the top tier, and nothing in there will save you from asking for the wrong thing very efficiently. It works on my network… if not on yours, fix it how you like. I’ll also entertain questions here or on my various socials, though my answers may not help in any meaningful way.

The first rule of The Foundry, it turns out, is that you talk about The Foundry: the entire value of the thing is that the agents report what they did, concede what they broke, and leave a paper trail a reviewer can attack. Tyler Durden would be disgusted. Your change-advisory board, for once, would not.

Header photo by Jakub Skafiriak on Unsplash. Not AI-generated; the sparks are real, which is more than I can say for my development team.