The Night Shift

Everything your crew has done so far, it did while you watched. Even the expediter's one-order pipelines ran with you at the pass, tasting at checkpoints. That's daytime service. But you've known since First Kitchen Lesson 8 that kitchens have another gear — the prep that happens before anyone arrives. Your Daily Special was a script on a schedule. Tonight, for the first time, a schedule runs a cook — an agent, with judgment, working unattended.

Read that sentence again, because this course owes you its honest weight: an unattended agent is a fundamentally more serious machine than an unattended script. A script does exactly its steps; a cook interprets. Interpretation at 3 a.m. with nobody at the pass is powerful and deserves the strictest rails in this course. Tonight is as much about the rails as the shift.

What you'll plate today

A real night shift: one read-mostly job your crew runs on a schedule — fenced, receipted, heartbeat-visible — plus the night-shift law that decides what's ever allowed to run in the dark.

Ingredients

• Your kitchen-brigade project, QC dial installed
• A genuinely useful overnight job — the survey your mornings would love pre-cooked: journal digest, folder inventory, the Prep Station board's heavy prep if you have one
• About 35 minutes

Cook

1. The night-shift law — before any scheduling

Write the NIGHT SHIFT law into CLAUDE.md before we build anything:

1. Night work is READ-MOSTLY: it reads, analyzes, and writes NEW
   report files into night-shift/out/. It never edits, moves, or
   deletes existing files. Daytime-me reviews; daytime-me applies.
2. The night kitchen is FENCED: it works inside this project only.
   Nothing outside the fence, no matter what it finds.
3. Everything is RECEIPTED: a run log with what it read, what it
   wrote, and its own honest note of anything it wasn't sure about.
4. QC still applies: STANDARD ticket-check minimum, run by the
   night crew itself, verdict in the log.
5. It ends every run by stamping the heartbeat: time, status,
   cook count.

Notice what rule 1 really does: it converts the scary version ("an agent doing things overnight") into the safe version — an agent preparing recommendations overnight. The night shift preps; the day chef decides. Every serious kitchen splits it exactly there, and so do we.

2. Rehearse the shift in daylight

The by-hand-first bar from Lesson 6, applied literally:

Create the call sheet "night-shift": [your job — e.g. "survey
yesterday's journal and meeting notes, cook the morning digest;
inventory new files in the drop folder; flag anything ⚠ that
needs a human"]. Full choreography under the night law — fence,
receipts, ticket-check, heartbeat.

Now run it RIGHT NOW, while I watch, start to finish. I want to
see exactly what 3 a.m. will look like.

Watch the whole run and read the receipts as if you'd just woken up: is the output what morning-you wants? Is the log readable half-asleep? Fix now — daylight is when night bugs are cheap.

3. Schedule it — the honest mechanics

Now the schedule. Explain the honest mechanics first: how does an
agent run without me pressing enter — what exactly starts, and how
do PERMISSIONS work when I'm not there to approve? Give me the
real options and their tradeoffs, then set up the safest one that
can still do this job: pre-approved permissions scoped to the
night law's fence — reads here, writes only to night-shift/out/,
nothing broader. Off switch demonstration before it's live.

Its answer is tonight's second lesson: unattended runs can't ask you mid-shift, so permissions get decided in advance — and the entire art is granting exactly the fence and nothing more. Scoped pre-approval for a read-mostly job in one folder is a rail; a blanket "skip all permissions" is a removed rail — that setting exists, and we wrote honestly about where it belongs; the night shift isn't it. Fence, not floodgates.

Then — fire-drill discipline — use the off switch: disable, confirm dead, re-enable.

4. The first real morning after

Tomorrow, before coffee: heartbeat first ("did the kitchen run?"), receipts second ("what did it do?"), plate last ("is it good?"). That reading order matters — it's the difference between auditing your night crew and merely consuming it.

Log: first night shift ran. Then tell me honestly, from the run
log: what would you do differently at 3 a.m. than you did in
rehearsal? Anything that needed judgment I wasn't there to give?

That second question routinely surfaces gold — "I wasn't sure whether the empty drop folder was an error or a quiet day" — and each answer becomes either a rule or a ⚠ flag. The night crew gets wiser one morning debrief at a time.

Save point: "the night shift".

When it burns

• Nothing ran — heartbeat stale — the First Kitchen classic wearing night clothes: laptop asleep. "Also run at first login if the overnight run was missed" — the morning version is nearly as good, and the heartbeat is what told you. Rails working.
• It ran but the output is weirdly empty — read its receipt before assuming a bug; a good night crew logs why ("drop folder had nothing new"). If the receipt can't explain the emptiness, that's the actual bug: tighten rule 3 until every surprise has a sentence.
• It asked for permission at 3 a.m. and hung until morning — the fence was drawn smaller than the job; the log shows which permission blocked. Widen that specific permission or shrink the job — never answer a hang with a blanket skip.
• You want the night shift to also apply its recommendations — the pull is real and the law says no, and here's the honest reasoning one more time: applying changes needs the one ingredient the night lacks — you. A morning where you apply three pre-cooked recommendations in two minutes is the win. Don't trade an audit trail for 120 seconds.
• This works so well you want five night jobs — the pantry rule's nocturnal cousin: each night job is machinery you must be able to audit half-asleep. One excellent shift you actually read beats five you skim. Grow by evidence, as ever.

Order up

□ The night-shift law is in CLAUDE.md — read-mostly, fenced, receipted
□ Full daylight rehearsal, receipts read with morning eyes
□ Scheduled with scoped pre-approval — fence, not floodgates
□ Off switch used, not just known
□ First morning: heartbeat → receipts → plate, and the debrief question asked

Next up — Lesson 09: Brigade Economics. The honest bill for everything this course taught: what a crew actually costs in subscription capacity, how to notice, and the judgment this entire kitchen has been building toward — when one cook is simply better.

Stuck on a step? Question box below.