The No-Code CAIO · Episode 002 — Tuesday, 7 July 2026

Series: Managing a team of agents · pt. 2 · Read time: about 4 minutes

Editor's Note

Last week I told you your AI agents need an org chart. A few of you wrote back with the obvious follow-up: fine, I drew one, now what? Fair. Churchill said "Give us the tools, and we will finish the job." The tools showed up. The job, it turns out, is management. Yesterday morning I sat across the table from two people I trust and tried to explain my week without sounding like I'd joined a cult. This edition is that explanation, cleaned up. Carpe diem.

Market Pulse

Strip away the computer science and an operating system is three promises. Every piece of work has one home. The rules don't depend on anyone's memory or mood. And nothing important happens without a decision somebody can point to later. Your business already runs on an operating system; for most of us it's the one between our ears, and it goes down every time we sleep.

Nine days ago I held a constitutional convention with my AI agents. I know exactly how that sounds. But before I let a crew of them loose on real work, I made them sit through the founding paperwork: a charter that says what they may do alone, what stops and waits for me, and where the work lives. We ratified it, and then we spent nine days making it true.

Here is what exists now, none of it written by me in code. One task board where every piece of work is a card with an owner and a next action; 57 cards on it as I write this. A button on my phone: one tap and a passing thought becomes a card on that board. I have run my life on sticky notes for decades, and I am typing this next to a monitor that, for the first time in memory, has none on it. A router that sends cheap questions to cheap models and saves the expensive one for work that deserves it; the cheap tier smoke-tested at $0.0002 a call. Two hundredths of a cent. And a vault, so I never again paste a password into a chat window like a caveman.

A demo works once. An operating system works when you're not looking.

Now the honest part, because this newsletter is not a highlight reel. Seven of nine modules run today. One is in a trial with a verdict date of July 11: adopt or drop, no extensions, and the trial data comes to me before the decision does. One more is fully loaded with the safety on; it produces nothing publicly until I approve its first run. I'm giving you the split on purpose. The gap between "it worked in the demo" and "it runs the business" is where most agent projects quietly go to die, and pretending mine skipped that gap would make me one more guy peddling wares.

Here's the position that will annoy the full-automation crowd: the gates are the product. My agents cannot publish, spend money, or touch a login. Ever. Those workflows all end at the same place, a named human decision, mine. I can count my gates on one hand: publishing, money, credentials, security, and adding a new agent to the crew. If you cannot list yours that fast, you are not ready to run agents, and "we'll see what it does" is not a plan. Please don't make it yours.

One example from the week, because a rule without a story is a poster. We had to harden the database that holds the task board. One agent staged the change and stopped. I ruled on it. A second agent applied it. A third verified it, before and after, and wrote the decision down. No agent grades its own homework. That habit is not artificial intelligence; that's a shop-floor practice older than I am, and it caught real mistakes this week. Just say'n: the best thing I brought to this build wasn't prompting. It was management.

An org chart tells you who does what. An operating system makes it stay true on a Tuesday when you're on the road and nobody's watching. Draw the chart, yes. Then build the building around it. The chart was the easy part.

Sidebar · The Seats — Five seats, one room of record

  • The Boss (that's you) — Owns every gate. The only seat that publishes, spends, or holds a key. Jason · human · phone + Slack
  • The Foreman (assigns & reviews) — Turns your intent into assignments, checks the receipts, keeps the record. Claude Design · chat mode
  • The Builder (makes things) — Stands up the plumbing and knows where everything lives. Pointers, never passwords. Claude Code · terminal CLI
  • The Hands (clicks the buttons) — The only seat allowed on the open web, one task at a time, receipts required. Codex · browser hands
  • The Records Desk (files everything) — Email, calendar, the knowledge base. If it isn't written down, it didn't happen. Claude CoWork · connectors

Sidebar · Steal These — Three workflows you can copy this week

  1. A thought leaves your head: Tap a button on your phone → It lands in a shared folder → An agent files it as a card → It sits on the board until done. The sticky-note killer. A card cannot fall off the plate.
  2. A risky change ships safely: One agent proposes → You rule: run / hold / revise → A second applies → A third verifies → Decision log. No agent grades its own homework. Ever.
  3. A work session runs: Open one thread, one topic → Each agent restates its task → Work + receipts in-thread → Stop at every gate → Written handoff at close. One room, one record. The handoff means tomorrow's session starts warm.