Thirteen years ago I packed away my knives for a keyboard. I still catch myself waiting to get found out.
I'm a cofounder now, building a company that puts teams of AI agents to work on real deliverables. The kind of work that has to be right. I've spent more than a decade in tech to earn that sentence, and on paper I'm still the least likely person in it. I don't have a computer science degree. My first career, long before this one, was a walk-in cooler and a chef's knife. When I tell people I used to cook, they smile the way they do when you mention you once did community theater. A nice detail. Not a credential.
Then one night Michael, my husband and the person I build with, got stuck.
He was chewing on the problem everyone in this field is chewing on right now. How do you get a crowd of AI agents to act like a team instead of a mob? Each one is capable. None of them is reliably in charge. They talk over each other, hand off work that's almost right, and produce something nobody can stand behind because nobody owned the whole. He was describing it to me at our kitchen table, of all places, and halfway through, the hair on my arms stood up.
I knew this problem. I'd lived inside it. A Friday night rush is a swarm of skilled people who can each sink the night on their own, and the professional kitchen beat that problem more than a century ago. I'd been fluent in the answer for half my life and never once thought of it as something I could carry out the door.
There were two halves to what I knew, and I'd never said either one out loud as a real skill.
The first half was fine dining. I cooked for Angela Hartnett at Cielo, Gordon Ramsay's restaurant on the top floor of the tower at the Boca Raton Resort, twenty-seven floors up over the ocean. A room like that teaches you something hard to fake: how a brigade turns a dozen separate specialists into one plate that lands in front of a guest at the right temperature at the right second, every service, for hours, while everything is on fire.
The second half is the one chefs don't put on the resume. After Cielo, I did the thing you're not supposed to admit. I went corporate. I took the franchise jobs. And even inside food, there's a chasm between fine dining and franchises. It runs deep. When I came back to a serious kitchen, Zazu, the Sonoma County farm-to-table restaurant run by Duskie Estes whose crew had just won the national Grand Cochon, I had to convince them I was still the same Stacy who'd cooked at Cielo. The corporate years were a stain I had to scrub off. I didn't understand yet that they were the other half of everything.
Because here's what the franchise taught me. I opened new locations and trained the people who'd run them. And when a franchisee was sinking, we took the keys: the parent company would step in, commandeer the restaurant, and run it ourselves until it was back to standard, then hand it back to the owner with a polite version of, here you go, try not to crash it again. I left the line for six weeks to go to a restaurant group's management school and learn how to run a kitchen at scale. Fine dining had already taught me how to be brilliant. The franchise taught me how to be brilliant somewhere nobody flew in to visit, on a Wednesday, for two hundred people, with a crew that turned over last month.
That distinction matters more than it sounds.
Here's what a kitchen knows.
There is always one voice. The person who runs a brigade during service is the expediter, and the French gave the role an honest name: the aboyeur, the barker. Tickets come in. The expediter reads them, sequences them, and calls the fire, timing every station so the five-minute plate from sauté reaches the pass in the same breath as the twenty-minute cut from the grill. The cooks don't coordinate through a hundred side conversations. They coordinate through one person who holds the whole night in their head.
Everyone owns one place. A cook owns their station and nothing else. The cold larder, the garde manger, isn't a vague region the grill cook wanders into when things get busy. It has an owner. You don't reach across someone's station, and you don't let your own go down. Anthony Bourdain wrote the truest line anyone's put to this: "Mise-en-place is the religion of all good line cooks." Your setup, the small ordered universe in front of you, is the difference between a clean service and a slow drowning. You build it before the first ticket so that during service you aren't thinking, you're executing.
Nothing leaves unchecked. The pass is the counter where the kitchen meets the dining room, the last thing every plate crosses before a guest sees it. The expediter inspects it, wipes the rim, sends it back if it's wrong. Thomas Keller will walk his own line mid-service to pull a loose thread off a cook's hat. That isn't pettiness. He understands that the standard is the product.
And when it works, it's quiet. Not silent. People picture a great kitchen as chaos and shouting, and that's the sound of a kitchen coming apart. But silence is its own alarm. It means the calls have stopped, and the expediter has gone blind to where every plate is. Quiet is the thing in between, and it's the sound of a line going exactly to plan. The expediter barks and every station has to answer. Anyone who's watched The Bear knows the grammar of it. Fire two. Yes, chef. Corner. Behind. Two minutes on the window, chef. Heard. Nothing moves on faith. Every call gets a word back. What you don't hear is noise. No chatter, no arguing across stations, no talking about your weekend. When you're on your station you're fully on it, speaking in a clipped shorthand everyone already knows, because the whole game is to keep the communication total and the noise at zero. At Alinea in Chicago they built the kitchen with nothing above waist height to block a sightline, because the best teams read each other and save their words for the work.
When Michael and I sat down to design how our agents would actually work, I stopped translating. I just described the kitchen I already knew. So that's what we built.
There's one expediter. A single orchestrator reads the work, sequences it, and calls each step. The agents don't negotiate with each other in an open room. They answer to the pass.
Everyone owns one place. We don't run pods. We never use the word. We run stations, each one a specialist with a defined job, and no station reaches into another's mise-en-place. The prep happens before the thinking starts. We settle most of the work the way a cook lays out a station before the rush, so the one genuinely creative step has everything it needs and nothing it has to guess.
And nothing leaves unchecked. Every piece of work hits a pass before it moves, a gate that fails closed. If it isn't right, it doesn't advance. It goes back.
The fine dining half of me built the brigade. The franchise half built the part people forget to ask for.
Fine dining is built to be brilliant every single night. That's the whole job, and it's harder than it looks. But it does it under glass: a small dining room, a Friday night in New York booked months ahead, guests who traveled to be there, a crew you hand-picked. The thing fine dining usually can't do is be brilliant for two hundred people in Montana on a Wednesday, with whoever showed up to work. That's a different discipline, and it's the one nobody romanticizes.
The best kitchens borrow it anyway. At the French Laundry, three Michelin stars, they've saved their recipes since 1985 and the cooks still measure everything, the chef says, "for consistency's sake and for training purposes." Even the pinnacle runs like a franchise underneath.
For a stretch of my career I walked into rooms where the standard had slipped and put it back. That's the other thing a system you can trust has to do. It has to do more than coordinate specialists toward something excellent. It has to hold a line, so the excellence doesn't ride on heroics or on who happened to be on shift. Standards written down and enforced, so the floor never drops. That's the governance under everything we build, and I recognized it long before I had the language for it, because I'd been the one sent to enforce it, clipboard in hand, smiling through my exhaustion.
This is the part I'll argue with anyone.
Most of the field is building crowds. Pods, swarms, crews, agents talking to agents until coordination supposedly emerges from the conversation. I get the appeal. It looks like a team. But a kitchen will tell you a crowd of talented people isn't a team, and you don't get consistent, trustworthy work out of a cluster negotiating with itself. You get it from bounded roles, one expediter, and a pass nothing gets past. We didn't land there from a research paper. We landed there because one of us spent fifteen years living it.
The feeling I started with hasn't fully gone. I'm not sure it's meant to. But it got answered.
The thing I couldn't explain, the reason a chef belongs in the room where the agents get built, turned out to be the whole blueprint. Both halves of it. The brigade I was proud of and the franchise years I used to hide. Michael brought the hardest problem in his field to our kitchen table, and I'd been carrying the answer the entire time, in an old knife roll and a stack of culinary textbooks. We didn't design a kitchen on purpose. I recognized one.
I didn't leave cooking behind when I changed careers. I just changed what comes out of the pass.