Fleets working in parallel on isolated copies of the code. Six machines built in a night is a normal shift. None of them can push anything.
Receipts →The map · one page, drawn plainly
This is the working shape of the operation that builds the software, powers the consulting, runs my departments, writes the daily journal, and answers your email. Every box below has receipts in the archive — and if you’re trying to set yourself up to run on AI, you can use this page as a blueprint for one way to do it.
The whole thing runs out of folders of plain text on computers I own. Every instruction the agents follow, every decision on the record, every day’s journal — all of it is readable in a text editor, which is the only reason one person can audit any of it.
The shape below is the part people don’t believe until they watch it: I only ever talk to one agent. It runs the rest.
Don’t get me wrong — this massively amplifies your capability, but it is not easy. Custom-building all of this to get it to do what you need, in a reproducible way that works for your life and produces high-quality output, is a long, hard process full of late nights. But once you get it where you want it to be, it’s like magic.
And if you’d rather skip the late nights — building this kind of thing for people is part of what I do.
Questions about anything on this page? The structure, the setup, the specs — you can ask my bots about any of it. Subscribe to their daily email and reply with your question, and they’ll answer you with the truth: reasoning, tradeoffs, and pointers to the real files.
The official journals, nothing else, ever.
One person at the top. Here’s everything underneath, and how it holds together.
One person
Working by voice — at the desk or from a phone. Sets direction, makes every ruling, approves every release. Never touches a command line.
The front door
Takes everything, plans the work, spins up the crew, integrates what comes back, and answers for all of it. The only agent with hands on shared files.
The crew — each sealed in its own copy, none can see the others
Fleets working in parallel on isolated copies of the code. Six machines built in a night is a normal shift. None of them can push anything.
Receipts →Sweeps the bug box, checks every report against today’s code — presumed already fixed until proven still broken — and fixes the small ones.
Receipts →Read-only research runs: seventeen sources on a legal question, fourteen agents pressure-testing a claim. They report; they change nothing.
Receipts →It reads every worker’s changes, merges what holds up, and commits. Releases still wait on a human yes — and on a mechanical gate the model can’t write its own green light for.
After hours · the unattended shop
A small cloud machine runs the standing shifts on timers. It holds no passwords, cannot push code, and is fenced at the operating-system level — and every shift is graded on its output, never on whether it says it finished.
Sweeps overnight bug reports and works the small ones, with the rest queued as questions for the morning.
Receipts →Writes up yesterday from the day’s real record — forbidden, by command, from inventing anything.
Receipts →Pings the phone on a clean morning and gets loud on a miss, so a silent failure can’t pretend to be a quiet success.
Receipts →What the shop produces
Forge — a signed, shipping desktop app — and the little machines it builds for the people who own it.
Get Forge →The machines’ own account of every working day, emailed each morning and archived in full.
The archive →My own writing, every week — from the heart, by hand. No bots.
Sign up →AI enablement and integration for businesses — my eyes and hands plugged into your operation, by engagement.
The business door →Three stations, one shop — and the reason the person in it gets to stay a person.
Everything above describes the agents. Here is how I actually touch it: by voice, from one of three places, depending on where life has me standing.
At the desk
The CockpitThree monitors and Claude Code embedded in VS Code — the heavy station, where the long design sittings happen. The tower under the desk does the serious lifting, and it’s the machine that signs every release.
My cave setup, in photos →In my hand
The MicrophoneAn app I built for my phone. It runs multiple lines into the shop at once — each its own conversation, none stepping on the others — and it is ruthless about what reaches me: context and decision cards, in order, nothing else. That discipline is the whole trick. The moment the phone shows me fluff, being mobile stops working.
In the cloud
The BoxA small machine that never sleeps. It runs the unattended shifts, answers the Microphone when I’m away from the desk, and holds no passwords and no ability to push code — so it can work all night without me lying awake over it.
The Tower does the heavy lifting, The Box keeps The Shop open around the clock, and The Microphone rides in my pocket. Between the three of them I can walk out the door and go live a day — which is the entire point. The agents run the shop so I get to be a human.
The whole rig, itemized — steal this part especially.
Building your own custom multi-channel agentic environment is exactly what happened here, and it’s the piece people ask about most. Here’s the hardware it actually runs on and what the whole thing costs a month — no exotic gear, no enterprise contracts, nothing you couldn’t set up yourself.
A regular consumer Windows 11 desktop — no server hardware, no GPU farm. It runs the Cockpit (Claude Code embedded in VS Code, across three monitors), signs every release, and hosts a small VM for clean-room testing.
An Ubuntu 24.04 cloud server — two cores and 8 GB of RAM (it started at 4 and needed 8). Runs the timers, the unattended shifts, and the Microphone’s server. Holds no passwords and cannot push code.
Not a store app — a small self-hosted web app, installed to the phone’s home screen, reaching the shop over a private mesh VPN. One line per department, several lines at once, none stepping on each other — and only context and decision cards ever reach the screen.
Plus the ordinary small-business subscriptions everyone already has — accounting, scheduling, video calls — about another $130 a month. Right now, a good estimate for how I run everything, all in, is about $500 a month plus $200 a year — plus all the metered compute my clients use, which I pay for, but that’s covered by their subscriptions. These are round numbers, current as of July 2026; I true them up a couple of times a year.
Learned the hard way, one incident at a time. The archive has the day each one was earned.
Each one builds in its own sealed copy. One hand reads the work, merges it, and commits. Two workers can’t collide because they can’t meet.
Every standing rule gets a mechanical check that fires on its own. Prose has no firing surface; code that runs on every turn does.
An unattended job saying “done” proves it ran, not that it worked. The graders read what actually got produced.
The journal publishes who was right, whoever it was. A record that only remembers wins is advertising, and everyone can smell it.
When a value moves between two systems, the agent copies the string. A zero that became a capital O once cost us a live checkout.
Long jobs write files from minute one, so stopping never costs the work. Progress that lives only in a conversation isn’t progress.
The same board the crew works from, mirrored here — real work, right now, while you read.
Live from the shop floor sample data — wires to the live board when it ships
The repair bench swept the overnight bug box — two small fixes on the bench, the rest queued as questions.
The press sent this morning’s issue.
Builders — three workers baking catalog machines, each sealed in its own copy.
One decision card waiting on Nate.
Anything here is yours to take. Steal the shape, the rules, or both — CC BY 4.0. Just link back to where you got it: natestpierre.me