Grand Opening

Two courses ago, a terminal was intimidating. Nineteen lessons later you've built pages by talking, given projects taste and memory, made every mistake reversible in two places, shipped to real URLs, built an app that listens and remembers, guarded its back room, had your agent inspect your work with its own eyes, shipped what a real guest asked for, and written procedures for your own crew.

First Kitchen's graduation asked you to ship something you chose. This one raises the only bar that matters now: ship something with guests. An app that listens, remembers — and gets used by at least two people who aren't you.

What you'll plate today

An app that didn't exist this morning: planned by interview, cooked from a menu, opened behind a real URL with a private pass — and, by the end, holding real entries from at least two real humans.

Ingredients

Everything from nineteen lessons (it's enough — it was enough last graduation too)
2–3 hours, one sitting if you can get it
Two people in mind. Actual names.

Cook

1. Choose a dish with guests in it (ten minutes, hard limit)

The shape hasn't changed since the last graduation — for a specific person still beats for everyone. But this time the dish must listen and remember. Three shapes that fit in one sitting:

The sign-up sheet — an RSVP for a real gathering you're actually hosting: dinner, hike, birthday, club night. Guests say in/out and a note; you read the tally on the pass.
The family board — a question of the week ("best thing you ate?"), everyone drops answers, the wall keeps them. Quietly becomes an heirloom.
The suggestion box — for your club, your team, your building. Anonymous-friendly, read from the pass. (Pointing this at your workplace works beautifully — and read the office recipe first for the etiquette of bringing your own tools to work.)

The trap, as ever, is ambition — accounts, uploads, payments are all wonderful later dishes. The test for tonight: can you name the two people who'll use it, and will it fit in one sitting? No and no means cut it down.

2. Open the kitchen like it's yours (because it is)

New folder. And this time the setup isn't a lesson — it's your standing procedure, dictated from memory in one order:

New project: [your dish, one sentence, who it's for].

Open the kitchen properly: CLAUDE.md with my house rules —
[dictate them; you know them by heart now] — save points from
minute one, mirrored to a new private GitHub repository.

Then interview me — five questions, one at a time — about the
guests, the feel, and what "done tonight" means. Then write
PLAN.md: three steps, plain words, each ending in something I
can see. Wait for my go between steps.

That one order is the entire first three lessons of this course, spoken fluently. Let yourself notice that.

3. Cook the menu

Step by step, with everything at your disposal, and the discipline you've earned:

One step at a time; touch nothing from later steps
The loop — look, say what's off, ask again — and the veto, both directions
Two kitchens: local pantry for tasting, online pantry for guests
Secrets set properly in both — never in files
Scope swelling mid-build? Smallest version that still delights.
Stuck or spiraling? Restore the save, smaller bite. You have receipts for everything.

When the build is done, don't type the closing routine — you have a crew now:

Set up my close-up and front-desk skills for this project, like
my card box has. Then: close up.

4. Open the doors

The pre-flight (stranger-read plus the honest what-could-a-rude-stranger-do question), then ship, then the ritual — with two people, each with a job: use the thing for real. An RSVP means they actually RSVP. Watch the pass as the entries land.

Two entries, two humans, one thing you built. That's not a course exercise anymore. That's operating software with users, which is a sentence that describes you now.

5. The last orders of the course

Front desk. Then add to CLAUDE.md a note titled "what the host
learned": three things I can do now that I couldn't when Dinner
Service started — ask me, don't invent them.

Answer for the you of six months from now. Then the one order no agent can run:

Tell the two guests thank you — and watch what they ask for next. That request list is your real syllabus from here.

When it burns

Frozen at the choice — same cure as last graduation, one level up: choose the gathering, not the app. What are you actually hosting, organizing, or wrangling in the next two weeks? Build its box.
It's 90% done and something's deeply weird — the graduate move, in order: save point, front desk (is data actually arriving?), raw rows from the pantry, then describe the end state fresh. Diagnose from evidence, not vibes — you have tools for evidence now.
Your two people are "busy" — they're not rejecting you; links sink in chats. Ask them in person or by voice, with the URL in their hand. Real software gets adopted one shoulder-tap at a time; this is true at every scale.
You're embarrassed it's "just" a sign-up sheet — the last boss again, and it still lies. Somewhere tonight, a team of professionals shipped a worse RSVP with a budget. Yours has a pass, a crew, receipts in two clouds, and users. Send it.

Order up — the final pass

□ An app YOU chose: it listens, it remembers, it has a private side
□ Kitchen opened from memory: rules, saves, cloud, plan — one order
□ Live at a real URL, closed up by your own crew skills
□ Two real humans used it — their entries are in your pantry
□ "What the host learned" is written in your own words

After the grand opening

Two courses down. Here's what's true: you don't need a course to build an app anymore — you need an occasion. They're everywhere: every sign-up sheet, every "reply-all if you're coming", every taped-up suggestion box is a dish waiting for a host who can cook. That's you now.

The recipes keep going deeper — new techniques leave this kitchen weekly.
Subscribe and they come to you.
Show us your grand opening at @AgentKitchenHQ — we mean it exactly as much as last time, and we read everything. What graduates build decides what this kitchen cooks next — including the next set menu.

And the question box below stays open, for this lesson and every one before it. Hosts' questions are how the next class gets a better course.

Service. 🍽️