Everyone prompts.
You’ll learn to operate.

Someone who read everything — and learned to finish sentences. A mountain of text, a machine that learned one game (guess the next word), and a chat window on top. Explain it at dinner without the word “algorithm.”

TRY IT · Ask the same question three ways; watch the answer change with your wording.

The best first draft in the world, of anything made of words. A menu consultant, not a cook — stop asking for answers, start asking for drafts. Answers you have to trust; drafts you get to judge.

TRY IT · Turn a messy 30-second ramble into a clean, friendly message in one pass.

No magic words — just the order ticket: what you want, who it’s for, what matters, what done looks like. And you get to send it back; a second draft costs one sentence.

TRY IT · Same request, twice: once bare, once as a full ticket. Compare plates.

The honest chapter. It can’t do anything, it forgets you, it doesn’t know your stuff, and it sometimes makes things up — confidently. Four walls, and every wall has a door.

TRY IT · Ask it to actually send the email it just wrote. Watch it apologize.

Every door from Chapter 4 opens: a stove (tools), an order pad (memory), your pantry (knowledge), a tasting spoon (checking). An agent is a chatbot with a kitchen and a work ethic.

TRY IT · Give the same ask to a plain chatbot and to an agent. Feel the difference.

Plan → cook → taste → adjust → plate. The trace is receipts for every step — you don’t watch it work, but you can always check how, not just what.

TRY IT · Replay your Chapter 5 run’s trace; find the moment it corrected itself.

The ticket comes back — and now it costs groceries. A vague ask gets the wrong dish cooked beautifully, so an agent’s ticket earns one new line: boundaries.

TRY IT · Fix a deliberately bad work order; run both; compare plates — and clocks.

Order from your home cuisine — commission work on a topic you know cold, find the one thing wrong (there’s always one), and send it back with one precise note.

TRY IT · Find the one thing wrong in the deliverable. There’s always one.

One cook, one banquet, one disaster. Stations fix it: slice work at the natural seams and give each specialist an index-card ticket with its own “done looks like.”

TRY IT · Split one oversized ticket into three station tickets; run it as a line.

What travels down the line is the tray: the work so far, plus a note. Grit passed at one seam is in everything downstream — check the seams, not the stations.

TRY IT · Read the trays: find what crossed 1→2 and 2→3 in your Chapter 9 run.

Nothing leaves the kitchen unless the chef tastes it. The plate that arrives is deliberately flawed — catch it, send it back in writing, and taste the rework.

TRY IT · Reject once, in writing. Watch the line fix exactly what you flagged.

Where the chef stands: gate what’s irreversible, sample what’s expensive, trust what’s checkable. Then bring a real piece of your week and ship it through your own line.

TRY IT · Your actual to-do item, done by your team, gated by you.

Dinner rush: a rail packed with tickets, stations firing in parallel, the expo merging plates at the pass. You cannot taste thirty plates — sampling is the skill.

TRY IT · Fire one question as ten tickets; sample the merged sheet hard.

The Sunday prep list: a ticket that fires itself on a clock. The design skill isn’t the schedule — it’s the bell, and the sous-chef’s checklist that makes it worth answering.

TRY IT · Design (on paper) your Monday-morning standing operation.

Good kitchens aren’t the ones where nothing breaks — they’re the ones where breaking is boring. Retry → re-route → ring; the only unacceptable failure is the quiet one.

TRY IT · Break a run on purpose; follow the ladder until it reaches you.

The capstone: a blank ticket and a real recurring chore. Design the kitchen, defend every choice, then turn it on. Graduate with an operation, not a certificate.

TRY IT · Design. Defend. Turn it on.