← All frameworks ~ operating system part 04 · the deployment blueprint

Seven ingredients. That’s the job.

Every AI deployment that fails, fails for the same reason: the recipe was incomplete. Not the tool. And every time I say that to an operator, they say the same thing back: “what do you mean incomplete? I gave it the instructions.”

Right. Here’s the thing. “Instructions” is one ingredient. There are seven. A recipe that’s missing four of them doesn’t work. It’s not that the tool is bad. It’s that you handed a new cook an instruction to “make the soup” without telling them what the restaurant is called, what the soup is supposed to taste like, what they cannot put in it, or whether anybody’s going to taste it on the way out. Of course the soup’s off.

These are the seven ingredients. Hit all of them and the dish holds. Skip any of them and you already know what failure mode you’re about to see.

An open handwritten leather-bound cookbook on a wooden counter, pages filled with ink in warm golden light, the professional recipe written down.

the recipe ~ written down, every ingredient in place

~ the deployment blueprint

The Professional Recipe, in one picture.

Seven ingredients. Two phases: Mise en Place (the setup) and Service Rhythm (the operation). Every recipe holds on all seven.

Part 1

Mise en Place ~ the setup

  1. 01

    Training House Style

    The persistent identity: who you are and what you stand for. Built once, referenced forever.

  2. 02

    Context The Ticket

    The situation-specific details of the individual order. Customer, job, history.

  3. 03

    Guardrails Safety Stops

    Hard-coded rules for what the station cannot do. The prices it cannot quote, the promises it cannot make.

  4. 04

    Examples Plated Reference

    Three to five real work samples showing what “good” looks like. This is the ingredient almost every operator skips.

  5. 05

    Format The Plate

    Describe the artifacts the station produces and the shape each one takes. The plate is the standard.

Part 2

Service Rhythm ~ the operation

  1. 06

    Escalation Hand-Back Rules

    Write the triggers, recipient, and payload for work that must leave the station and go to a human.

  2. 07

    Feedback Taste, Then Revise

    Track two to three value metrics, then use every miss to update the ingredient that broke.

~ seven ingredients, two phases

The ingredient almost every operator skips.

Examples. Ingredient #4. In every single audit I’ve run, this is the lowest-scoring ingredient. Everyone writes training. Everyone adds context. Most people forget examples entirely, and examples are literally what tells the station what “plated well” looks like in your business specifically. Three to five real samples of good work. That’s it. Add them this afternoon and you’ll watch output quality jump tomorrow.

Each ingredient, a little deeper.

Training (House Style). The persistent identity of the station. Who the business is. How it talks. What it stands for. This is the foundation. Written once, referenced on every ticket.

Context (The Ticket). The situation-specific details of this order. Customer history, job notes, the thread so far. Context tells the station which customer is standing at the counter right now.

Guardrails (Safety Stops). What the station cannot do. Prices it cannot quote. Promises it cannot make. Actions that require the Chef’s eyes. Without guardrails, the station can do anything, including things that blow up the business.

Examples (Plated Reference). Three to five real samples of what “good” looks like in your business. Not generic best practices. Your actual plates. This is the ingredient that separates generic AI output from output that sounds like you.

Format (The Plate). Describe the artifacts the station produces and the shape each one takes. A request, a reply, a memo, a log entry. The plate is the standard. The path is the station’s problem.

Escalation (The Hand-Back). The rule set for which dishes leave the station and go to a human: what triggers the hand-back, who receives it, and what travels with it. Escalation is what makes the other six ingredients safe to run.

Feedback (Taste, Then Revise). Two halves: instrumentation and revision. Track two or three metrics that map to value, then treat every miss as recipe data. Which ingredient broke? Update that ingredient, then run the next ticket against the sharper recipe.

Hit all seven and the dish holds. Skip any one and you already know the failure mode.

How it connects.

The Recipe is what you write when you move from Doing to Dispatching. The Four D’s says Dispatching is when you write the recipe. Dialing is when you refine it. The Prep List tells you which recipe to write first. Quality Control diagnoses which ingredient broke when the station drops a plate.

~ the monday move
Take the dish your Prep List picked. Write the recipe, all seven ingredients. Deploy it. Watch it run.