Quality Control

Time to name the crew's quiet failure mode, because everything until Lesson 10 depends on managing it: cooks want to please you. Ask an agent "is this right?" and the gravity pulls toward yes. Ask it to summarize, and it will summarize something even when the source was thin. This isn't lying — it's agreeableness, and one agreeable cook is manageable because you taste everything. But you're building crews now, and plates pass between stations without you — the merge cook trusts the parallel cooks, the expediter trusts the merge. Agreeableness compounds in the dark.

Restaurants solved this centuries ago: the plate meets a checker before it meets the guest — someone comparing plate against ticket, whose job is finding problems, not making friends. Your Inspector already does this for finished work. Today, checking becomes a station inside the choreography — and you learn the adversarial trick that catches what polite checking misses.

What you'll plate today

Two checking patterns wired into your call sheet — the ticket-check (does the plate match the order?) and the adversarial pass (can a motivated skeptic break it?) — plus the calibration for how much checking a job deserves.

Ingredients

• Your kitchen-brigade project, expediter running
• A claim-heavy piece of real work — a survey result, a report with numbers, anything asserting facts
• About 30 minutes

Cook

1. The ticket-check — plate versus order

The cheapest check in any kitchen — did they make what was ordered?

Add a TICKET-CHECK station to the survey call sheet, between merge
and Inspector: a fresh subagent gets the ORIGINAL order and the
plate — nothing else, not the working files — and answers only:

1. Does the plate answer the question actually asked?
2. Is everything the order required present? List what's missing.
3. Did anything sneak in that wasn't ordered?

Pass/fail per item. A checker never fixes — findings go back to
the station that cooked them.

Feel the design: the checker sees order and plate only. Show it the working files and it inherits the cook's context — and starts sympathizing with why the plate drifted. Cold comparison is the whole power; you learned this in Lesson 1 and it's still the deepest trick in the book.

2. The adversarial pass — hire a skeptic

Ticket-checks catch drift. They don't catch confident nonsense — the plausible number, the citation that isn't quite there. For that you need the strongest move in quality control, and it's a personality transplant:

Run an adversarial pass on [your claim-heavy work]. A subagent
with this exact stance: "This document is WRONG somewhere. Your
job is to find where. Check every number against its source,
every claim against the file it cites. You get no credit for
'looks fine' — you get credit for catches. If you truly can't
break something, say what you tried."

Findings numbered, evidence quoted. Its job is the attack; the
verdict on each finding stays mine.

Read the results carefully — including the misses. An adversarial cook will stretch to please you with catches (agreeableness again, aimed the other way!), which is why the verdict stays yours. But among the stretches there's usually one real catch that polite review sailed past — a total that doesn't sum, a "the data shows" that the data doesn't show. One real catch, before it shipped under your name: that's the station paying rent.

3. Calibrate the paranoia

Checking costs cooks, and not every plate deserves a security detail:

Write the QC dial into CLAUDE.md, three settings:

- LIGHT (my own reading): drafts, internal notes, anything I'll
  taste line-by-line anyway.
- STANDARD (ticket-check): anything a call sheet produces —
  automated work always gets at least this, because nobody tasted
  it on the way.
- FULL (ticket-check + adversarial): anything with numbers or
  claims that ships under my name, and anything a colleague will
  rely on.

Update the survey call sheet to say its setting. Default: STANDARD.

The middle rule is the load-bearing one: automation always gets at least a ticket-check, precisely because automation is where your tasting used to be. Hand-cooked work has your eyes by definition; machine-cooked work has whatever checking you wired in.

4. Close the loop

Re-run the survey call sheet end to end on fresh input — now with
the ticket-check wired in and the QC setting declared. Save point:
"quality control".

When it burns

• The checker failed a plate that's actually fine — checkers err strict; that's the correct direction (a false alarm costs a re-look; a false pass costs your name). Adjudicate, and if a pattern of false alarms emerges, calibrate the checker's file like any specialist.
• The adversarial pass returned twelve "catches" and they're all stretches — the credit-for-catches incentive overheating. Add the honesty valve to its stance: "quality over quantity — one confirmed catch outranks ten maybes; label each finding CONFIRMED or SUSPICION." The label discipline fixes most of it.
• Cook and checker disagree and re-fire loops forever — two rounds max, then it escalates to you with both positions quoted. You're the chef; standoffs are yours to break. Add the two-round rule to the call sheet.
• This all feels slow now — the QC dial is the answer, and honestly: yes. Checked work is slower than unchecked work — in kitchens, in code, in crews. What you're choosing is where to spend slowness. LIGHT exists for a reason; so does FULL.
• The adversarial cook found an error in work you already shipped — breathe; this is the good timeline. You now know before your colleague's Friday meeting does. Correct it, send the update, and notice the QC dial just calibrated itself: that category is FULL from now on.

Order up

□ Ticket-check station wired into the call sheet — order and plate only
□ One adversarial pass run — stretches judged, real catches found
□ The QC dial is law: automation never ships below STANDARD
□ Call sheet re-run end to end with checking built in
□ Save point "quality control"

Next up — Lesson 08: The Night Shift. Your crew works while you watch. Next lesson it works while you sleep — scheduled crew runs, and the stricter safety rails that unattended cooking demands.

Stuck on a step? Question box below.