This is for anyone handing real work to AI chats. I'm building Bravilo, a workout app, alone. Fifteen chats in Claude write its code, tests, website, videos and App Store text. Since September they have broken things no single chat would break: pushing each other's half-done work, answering one question two ways, running tests on top of each other. Each break left a rule. Here are the rules, and the cycle they add up to.
Every chat, every job
None of the chats decides anything. I do. But at the start, no chat had a job of its own.

In early October, I opened CircleCI and Vercel and saw my credits would run out in two days. Every chat was pushing its own work the moment it was done, and every push started another build. My first thought: I'm pushing far too much code through each chat. I couldn't keep track of what each one was doing or where their conflicts came from, and every one of them pushed its work to test on its own, burning through my CI credits.
So each one got a job, and a line it must never cross
Most of what broke for me started when a chat did the job next door. So the never line matters more than the job.
QABreaks it before you can.
BuildWrites the code you never see and always feel.
Build 2Makes the app feel good in your hand.
WebsiteOur front door, and the one counting who walks in.
StudioOur film crew of one.
GrowthOur voice in the world, and its fact-checker.
Chief of StaffKnows who's doing what, so I don't have to.
ResearchFinds the evidence before we decide.
Creative DirectorThe taste police, with a moodboard.
FinanceMakes sure the receipts add up and the taxman stays happy.
LegalOur privacy guardian, armed with GDPR.
Head TrainerMakes sure every exercise is one a real trainer would sign off.
But I didn't write the rules up front. Each one arrived after something went wrong.
Everyone through one door
Release One push per round

Pushing the moment the work was done felt fast. But one chat's push carried the others' unfinished commits along with it, and half-built work reached the test server. All those pushes, so close together, used up Vercel's daily deploy limit.
So on 9 October the door got narrower.
Two answers, one sore knee
Issue One book of answers, read first
On 14 October I asked one question. What should the coach say to someone with a sore knee, on a day the workout needs no changes? Two chats heard it. Each wrote an answer, and each sounded kind and sure. Only one matched what the app actually does.

So answers now live in one book that is only ever added to. A changed answer gets a new line that names the one it replaces. There are more than 970 lines since 23 September, and the chats look a question up there before they bring it to me.
Two hands on one blackboard
Review Tests that count read alone

Then tests began to fail late in the evening, and nothing in the code explained why. Two chats were running them at the same moment, writing to the same test database. A test that counted rows found someone else's rows in the middle of its count. Every failure looked like a bug in the feature. They were collisions.
The fix was small: those tests now read inside their own transaction. And every change passes two helpers before it's committed. One runs the checks and reports only what failed. The other reads the change against its issue.
A yes from my phone
Release A yes covers one action
By November the first release was close, and I wanted it to move fast. On 4 November I decided Chief of Staff could push for me when I said yes from my phone, away from the laptop.
That made a yes worth more, and easier to borrow. Chats message each other when they're blocked or done, and some of those messages read like approval. So the same day, the rule went into the book.
The cover that said twelve
Posts Every public line passes a claim check

Growth writes what Bravilo says in public, and every caption goes through a claim check before I see it. The carousel that introduces this team said "Twelve AI chats" on its cover. There are fifteen. One slide said the trainer chat "checks every exercise", which could read as a human trainer's sign-off.
The cover now says "Twelve of our AI chats". The slide says it reviews exercises "the way a trainer would". I post it myself, after the check.
Evening, three lists
Every decision still waits for me, and that's deliberate. The chats are fast, and they sound just as sure when they're wrong. I'd rather wait a few hours than send a line to someone's phone that the app can't back up.
Since 29 October, every daily chat sends Chief of Staff three lists at the end of the day: done, blocked, and waiting for me. What reaches me is one short status, with only the things that need a decision.
I could have merged them into fewer, bigger chats that each see everything. The week before, I measured what that costs. Most of the spend went on the chats re-reading their own history: a median of 540,000 tokens on every step, 80% of all usage. Running the checks cost about $530 inside the big chats, and about $20 in a small helper. Merging would have made every chat bigger, and every step dearer.
So on the same day the chats got smaller instead:
- A fresh chat for every issue. Build and QA start clean on each issue, so no chat carries old work into the next one.
- Checks in a small helper. A helper on a cheaper model runs the type checks, lint and tests, and hands back only what failed. A second helper reads each change against its issue before the commit.
- One everyday model. Most chats run on the same model. The strongest one is called by name for a hard problem, and is the default only for the two design chats, the Architect and the Creative Director.
- One status for me. Chief of Staff gathers the three lists, so I read one note, not seven chats.
The idea behind all four is the same: keep each chat's context small, and send repeat work to something cheaper.
When one part of the app keeps coming back broken, I can pause the one-at-a-time fixes there. The Architect writes out options, and I pick one.
The whole round
- Ideaanyone finds it
- Issuemy yes
- Buildone issue, one chat
- Reviewtwo helpers
- QAnever writes code
- Releasemy yes
- Postsmy yes
Now I deal with Chief of Staff for everything and keep an eye on how it all runs. I worry a lot less about one chat walking into another's work, or two of them doing the same job.
Which line has your AI crossed? Tell me on LinkedIn or X.
Bravilo opens on the App Store soon: bravilo.app.