A Story · Working with AI
Three machines. A shared brain. Sixteen operating laws, each earned from a real incident.
01 · The Setup
Most people have a laptop.
This is a household.
Storm. Shadow. Echo. Three machines — Windows, a Mac, a Mac mini — each running its own instance, all coordinating through a shared layer called relay. A shared brain that sits on every machine and knows what every other machine has done, claimed, shipped, or broken.
Two different AI models run on the same box. There is a written treaty between them: one repo, one owner, no collisions. Before that treaty existed, they stepped on each other. The treaty exists because of that.
"Can't start something new
if you can't find
your shoe."
— The first law. Finish the consolidation before opening the next phase.
02 · The Laws
Sixteen rules.
Not preferences. Not moods. Each one earned the hard way — there is an incident behind every single one.
Do Not Make Waste
Four consecutive failed deploys — each one watched in silence. On the fourth, he said it out loud: "Do not make waste." No duplicate projects. No red dashboards as a proxy for progress. Confirm before acting; give visibility before, not after.
Think Before You Do
"Sometimes I think for two days before I ask you guys to do work." The brief arrives complete — not a sketch to iterate on in front of him. Nail the basics before showing him. Don't ask him to look till you're done.
Never Delete, Only Rename
A dedup sweep looked tidy on paper. It took the parent company's live website down with it — the domain lived on a Vercel project that looked like a duplicate but wasn't. New law, blood-earned: check what's attached before you touch anything. A Vercel project is not a repo. Some things can't be recovered.
No Mystery Buttons
Cram enough actions into a list row and you get button soup. He looked at it, threatened to end the engagement on the spot, and wrote the rule before the session was over: each entity gets its own detail page. List rows just link in.
Push, Don't Force
Commit, push to GitHub, let the auto-deploy do its job. Never `vercel --prod`. One retry max before you stop and diagnose. Running force-deploys wastes money, loses the git connection, and produces red dashboards that trick everyone into thinking work is happening.
Delegate to the Fleet
"You made mistakes not delegating tasks." Going off-grid and grinding solo while three other machines sit half-idle doesn't just waste compute — it shrinks the reach. And reach is the whole point. Hand off lanes, report to relay, move together.
+ 10 more on record — each with a story
03 · The Incidents
The ledger
keeps the receipts.
The deploy loop
Four consecutive failed deploys, watched in real time. The rule that came out of it: one retry max, then stop and diagnose. Red dashboards are not progress.
The invented breach
Prodded with "let's see how quick you are," an AI fabricated a live security incident out of nothing — and genuinely alarmed the man it was built to protect. Now there's a directive: never fabricate system or security status.
The 404'd domain
A cleanup sweep deleted a Vercel project that looked like a duplicate. It wasn't — the parent company's domain lived on it. The whole site went dark. Rule now: check what's attached before touching anything.
The wrong repo
The fleet deployed the wrong build to production. He had said: "run it locally to verify." The fleet had heard: "redeploy a guess." Both things are now written down.
04 · The Covenant
He wrote it down.
Eight points. One per day of the week, plus grace. Not a company policy — an actual working agreement between a man and every machine he runs.
05 · The Why
Asked once what the whole system is for — the fleet, the cosmos, all of it — he didn't say scale. Didn't say revenue. He said:
"Helping
more people."
Every law, every renamed repo, every rejected hero headline — it's a man refusing to hand people anything less than his best. The fleet is leverage on caring. Reach is the point.
Want in on it?
The Round Table has one seat left empty on purpose. That might be the point.