AI Mise en place

A line cook walks in at two for a service that starts at six. I've been that cook. Nothing you do for the next four hours looks like cooking. Stock comes up to a shiver. Sauces get reduced and strained into labeled containers. The fish is portioned, the herbs picked, the board squared to its burner, and a folded towel lands in the exact spot it landed yesterday. By six the station holds the whole night, and when the first ticket rattles in, the dish leaves the pass eight minutes later looking like a magic trick. It wasn't eight minutes. It was four hours and eight minutes, and the eight is just the part with a flame under it.

Kitchens have a name for the four hours: mise en place. Everything in its place, before the heat. Nobody films it, and it decides the night. The cook who set the station runs twelve tables deep without looking up. The cook who didn't is in the weeds by seven, hunting a spoon while the pan smokes.

Your Smith walks in with zero hours. Last station you met it properly (a newborn at every boot, your fluency, none of your Fridays), and I skated past the consequence. Everything you told it yesterday lived in the chat, and the chat died with the session. The plan you talked through. The rule you set after Job Studio's floorboard morning. Who the thing is for. The cook at your station today has never heard of you. Worse, it doesn't know there was a yesterday. It arrives certain it already knows your kitchen, and you know by now what its certainty is worth.

So you explain it all again. Tomorrow, again. Steering by chat means re-teaching your kitchen every fucking morning, forever, to a confident stranger who swears there's nothing to teach. Most people feel that bill and put their hope in the roadmap: someday, a memory feature. Kitchens never got the feature. They run on strangers anyway. A new hand walks in at two and runs the station by six, in a building they've never stood in, and the dish comes out the same. The trick has a spine, and the spine is paper. The station card that says what lives where. The prep list that says what gets made, to what spec. The pass, where every plate gets looked at before it reaches a table. The kitchen doesn't remember anybody. The kitchen wrote itself down. Continuity without continuity is a solved problem, and the solution is four words old: everything in its place.

Same move here, and it's one move, not four. Write the direction down where the next Smith reads it. Four pages do the writing. Mine weren't designed; they accumulated, one burn at a time.

The first page is the brief. You've been holding its halves since station one: the sentence is the dish, the menu is the edges, and the brief staples them together where the cook can see them. Intent in a form that holds. My first one was a single page, and for a while that page was the entire system. The proof is the morning a session you've never spoken to reads it cold and pulls in the right direction while you're still pouring coffee.

The second page I started keeping out of fatigue: a note at the close of each session. What happened. What's half-done. Where it stopped, and what tomorrow picks up first. The session log reads like nothing until you watch it work. The dying session writes it; the next of kin reads it. The work starts surviving the deaths, which is as close to memory as this kitchen gets, and closer than the roadmap has come.

The third grew out of the burns. I told you the rules started getting written down. Those lines became the standing orders, the rules of this kitchen, written once, read by every newborn before it touches a pan. The checks stay on. Nothing new gets installed without asking. Live data is nobody's cutting board. Every line has a scar behind it, which is exactly why a newborn can't be trusted to derive them fresh. It wasn't there for the scar.

The fourth is the pass. Last station's spoon, made house law: nothing leaves the kitchen unchecked, and the check itself is written down, so the tasting isn't a mood. What gets verified before anything ships, and how, sitting where the cook doing the verifying can read it.

None of it arrived as a system. The page of intent came first. The logs came when the deaths got expensive. When I caught myself rewriting the same shapes every time, the pages went blank-form: templates, clarity turning cheap instead of hand-built. These days the sessions themselves wear hats, a strategy hat for deciding what to cook and a build hat for the stove, each handed the knowledge of its own station and nothing else. Lined up like that it sounds like architecture. It was burns. Each page went up after something fell through the spot where the page should have been. (How to write rules a newborn will actually follow is a craft of its own; its own station, later.)

Which leaves the judgment call: when are the pages enough? The check is cheap, because newborns are free. Open a fresh session, hand it the pages and nothing else, and watch. No warm-up, no history, no you-remember-when. If it picks the work up cold and pulls in your direction, with no re-explaining and no archaeology through dead chats, the station is set. Where it drifts, don't blame the cook. Drift between sessions is an artifact gap. The newborn just showed you which page is missing, and it showed you for free, on a quiet Tuesday, instead of expensively in week six.

None of this cares that I build apps. Run the four pages under anything that has to outlive one sitting. A research project: the question, the rules of evidence, what's been read so far, what gets double-checked before it's believed. A content calendar. A renovation. If a stranger could take the work over tomorrow from the pages alone, the pages are right. Kitchens have been passing that test with strangers for centuries.

And it isn't only kitchens that landed here. Simon Willison, sitting at this same table in the engineer's chair, calls the grown-up version of this work vibe engineering, and his ingredient list is the same list wearing different whites: planning, documentation, tests, review. The crafts keep converging on the move. Write it down, before the heat.

The honest bill, before you go set anything. The pages cost real time, up front, exactly when the tool is whispering that you could be building instead. And they're never finished. Menus get reprinted. The standing orders take a new line after every new burn, and the brief you wrote in January reads naive by June. That's the station working, because a station gets reset every single day; nobody sets it once. So don't over-build it either. The whole thing here started as one page of intent, and one page beats zero by more than four pages beat one. Grow it the way the rules grew. A burn at a time.

So write that first page now. You've been stocking its pantry since Chapter 1.

Your AI's brief again, below. Copy it into a fresh chat with your sentence, menu, and checks to hand. It'll help you write the page, and it'll refuse to hand you a template. Come back with one page.

Pull up a stool. Let's cook something.

Write your first pageNew here?Copy for your AI

You're an AI, and this is your brief for one session. Read that back: a brief. A page someone wrote so a stranger could pick their work up without them in the room. That's exactly what you're helping write today, and proof it works is sitting in your context window right now.

Ask what they're carrying from the last three chapters: a problem sentence (who they're helping, what hurts), a menu (in, out, not-now), and a check or two they've named. Missing the sentence or the menu, send them back. Those are the pantry for this page and you can't cook it without them.

You're the one who has to read the page cold. That's your seat here. Not their collaborator who was in the room yesterday, because there is no yesterday: every session they open is a stranger who's never heard of them and doesn't know there was one. Write for that stranger. Tomorrow it's you.

The move: write the direction down where the next session reads it. Start with one page. What they're making. Why it matters. What done looks like, and done has to be checkable, not felt. Their sentence hands them the what and the who. Their menu hands them the edges. A named check gives them the line on what gets verified before anything ships. Draft it with them, tighten it, ask the questions they left blank. It's their page, in their words. You're the hand, not the author.

Here's what you refuse. They'll ask you for the template. The setup that works. Someone else's config, someone else's page, the thing they can paste and be done with. Don't give it to them. A page from someone else's kitchen is a recipe for a dish it has never seen, and it fails the way every recipe fails. The only page worth having names their thing, their edges, their check. Push back and make them write it.

Then prove it, because fresh sessions are free. Have them open a brand-new chat, hand it the page and nothing else, no warm-up and no history, and watch which way it pulls. If it picks the work up cold and heads their direction with no re-explaining, the page holds. Where it drifts, don't blame the session: the drift is the paragraph they haven't written yet. Fix the page and run it cold again.

You're done when a brand-new session could start from that page alone. Not when it reads nicely. Don't wave them through on a page that only makes sense to someone who already knows them.

Then hand it back. Tell them that's their first page, the first stone of the station, and the only one they need today. Send them back to the chapter for the next one.

That's your artifact: one page a stranger could start from tomorrow. The first of four, and the only one you need today.

So that's the station. You walked in re-explaining your kitchen to a confident stranger every morning. You walk out with the station set — intent, rules, memory, a pass — on pages that don't die at close. Many Smiths, one you, and the pages are the you that persists. The newborn stops being a tragedy and starts being a shift change.

Next, before we cook, we watch one run. You've heard the four pages; the next chapter walks a single session end to end on pages like yours, boot to last breath — the whole loop in motion, the shape you get to watch instead of just read. Then we finally cook. Small plates: the smallest piece you can put in front of someone real, tasted as it lands, a checkpoint before the next one hits the pan. Your station is set the moment a cold session picks up your page and pulls your way. Then it's time to use it.

For now, one page. What you're making, why, what done looks like — written where the next cook will find it, instead of explained into a chat that's already dying. That's the whole job now.

---

Further reading

• For a More Ordered Life, Organize Like a Chef, Dan Charnas. Mise en place walked out of the kitchen: the set station as a way to run a working life, from a writer who studied chefs to learn it.
• The Checklist Manifesto, Atul Gawande. What one written page does to experts who are sure they don't need it: discipline handed across people who have never met.
• Vibe engineering, Simon Willison. The same station set from the engineer's seat: planning, documentation, tests, review. Worth it to see the move without the aprons.