The 15-minute version · page 11 of 15

Chapter 11

Going Vertical

When people first get AI, they use it to rebuild what they already know, only faster. The most tempting version looks modern: a fleet of agents, each with a title. A CMO agent, a CFO agent, a COO agent, each on its own island. It sounds like the future. It is the past. It copies the org chart into software and rebuilds every handoff we have always lost work in.

Role is the wrong seam. A CFO agent and a CMO agent both need last month's numbers, and real questions do not arrive by department. The only good reason to split work off is a wall around permissions. A different job title is not a wall. It is a costume. So I went the other way: one agent per project that does every role, builder, tester, bookkeeper, the one who answers on a Tuesday, and because it is one agent, it holds the whole picture with nobody to catch it up. The project's folder is both what it knows and the wall that keeps it safe.

The system is named Ambrose, after my ninth great-grandfather, a ship caulker who sealed the seams so a vessel would hold against the sea. The name is a standard: do honest work, and do not hide the seams you have not sealed. Caulk the seams.