Run sheet One day For whoever is delivering it · not a student page

A Day With the Twelve

How the long trail runs in a room, with a clock on it. The twelve pages are written to be worked at any pace; this one puts them into a day and says what to drop when the day runs short.

Emile du Toit
brainitconsulting.com
brainit-aiworkshops.vercel.app/run

Nobody leaves having watched. Everybody leaves with a folder on their own laptop, an undo behind it, and something they built in it.

01The arithmetic, before anything else

Twelve workshops do not fit in a day. It is worth knowing the number rather than discovering it at three o’clock.

630 minutes

Ten hours and thirty minutes — of labs alone

That is the sum of every lab timing across the twelve pages, before a word of teaching, before questions, before somebody’s laptop refuses to install Git. A seven-hour day with lunch and two breaks leaves about 345 minutes of actual room time.

So a day is #001 to #007, honestly done, with the rest sent home. Anybody who tells a host they will cover all twelve in a day is going to be wrong in front of a room.

Where the time actually goes

Workshop	Labs	Lab minutes	In a day?
#001 The Horse in the Field	5	60	Yes — all of it
#002 Saddlebags and the Ride	4	50	Yes — Lab 3 demoed, not worked
#003 Why Leave the Field	3	35	Yes — all of it
#004 Inside the Tack Room	4	40	Yes — the install is the lesson
#005 The Horse That Opens Gates	4	55	Yes — the heart of the day
#006 Driving the Working Horse	4	65	Partly — Lab 4 is a week, send it home
#007 Breadcrumbs	4	50	Partly — first to be cut
Sent home, with the pages to work from
#008 Drawing the Trail Map	4	60	Home — and it is the one that pays
#009 The Well	4	55	Home
#010 Taking the Wagon to Market	4	45	Home
#011 Riding the Fences	4	55	Home
#012 Who’s at the Gate	4	60	Home

Say this out loud at the start “We are doing the first seven today. The other five are written down on the same site, in the same shape, and you can work them at your own desk. Nothing after today needs me.” People relax when they know the shape of the thing. They get anxious when they suspect they are being rushed.

02The day, with a clock on it

Nine thirty to half past four. Adjust the start; keep the shape.

Time	Minutes	What
9:30	20	Arrive, coffee, laptops open. Not teaching time. This is where you find the two people whose laptops are locked down, and it is why it exists.
9:50	55	#001 The Horse in the Field. All five labs. Do not rush the standing instructions — it is the one that changes how they use it forever.
10:45	15	Break
11:00	40	#002 Saddlebags and the Ride. Labs 1, 2 and 4 worked. Lab 3 — the twenty rows — demoed on the screen, because the point lands watching.
11:40	35	#003 Why Leave the Field. The folder gets made properly here or nothing after this works.
12:15	45	#004 Inside the Tack Room. The VS Code install. Budget generously; this is where a day either stays together or does not.
13:00	45	Lunch
13:45	60	#005 The Horse That Opens Gates. The heart of it. The permission prompt, and one real job start to finish.
14:45	15	Break
15:00	45	#006 Driving the Working Horse. Labs 1–3. Lab 4 is a week of real use — that one goes home.
15:45	40	#007 Breadcrumbs. Git installed, one marker, break it and get it back. GitHub if the clock allows.
16:25	5	Close. One sentence each: what you are going to build. Then the site, and the five workshops still on it.
16:30		End

The two soft spots are 12:15 and 15:45. The install can eat twenty minutes you did not have, and Breadcrumbs is last so it absorbs everything that went before. Watch the clock at lunch: if you are behind by then, you are cutting from the list below, not catching up.

03Stop by stop — what you do, and what they do

The pages carry the content. This is only the difference a room makes.

#001 — The Horse in the Field

Demo: nothing. Everyone is in a browser tab and everyone can keep up.

Worked in the room: all five labs. Lab 2, the standing instructions, is the one to protect — it is twenty minutes and it is the most valuable twenty minutes of the day.

Watch for: Lab 3 asks about a report that does not exist. Both chatbots search the web now, so you may get a clean refusal rather than an invention. Both outcomes are on the page. Try it yourself the week before so you know which one the room is about to see.

#002 — Saddlebags and the Ride

Demo: Lab 3, the twenty customer rows. Paste them on the screen, ask it to “tidy up the list”, and let the room watch it merge the two Ken Whitfields. That lands far harder watched than worked, and it saves you ten minutes.

Worked in the room: Labs 1, 2 and 4.

The line worth saying: the danger is not that it makes a mistake, it is that it makes the same mistake at speed, evenly, across everything.

#003 — Why Leave the Field

Demo: chapter one, read together. Dale’s six files are on the page with copy buttons — put them on the screen so people see what a working folder looks like before they make their own.

Worked in the room: Lab 2, the folder. Go round the room and look at every one. A folder made wrong here is a broken afternoon at 13:45.

Watch for: anyone with nothing of their own to put in inbox/ and reference/. Point them at Dale’s files — that is exactly what they are there for.

#004 — Inside the Tack Room

Demo: the install, on the screen, one step ahead of them. Say “yes, I trust the authors” out loud before it appears, or six hands go up at once.

Worked in the room: all of it. This one is the install.

Watch for: the work laptop with no administrator password. There is no fix in the room. Pair them with somebody, and make sure they still leave having watched every step — they can do it at home on their own machine.

#005 — The Horse That Opens Gates

Demo: the first ride, on your screen. Claude Code needs a paid plan, and a free ChatGPT account only gets Codex for quick tasks, so you run it and everybody watches. Ninety seconds, and it is the clearest picture of the difference they will get all day.

Worked in the room: Labs 2, 3 and 4 — on the free route if they have not paid, which most will not have. Nobody should feel behind for it.

The moment: Lab 2, saying no to the permission prompt. Do it on the screen first, then let them. Forty seconds, and it is where the room relaxes.

#006 — Driving the Working Horse

Demo: Lab 1, both halves. Read the bad instruction out, ask them to guess what comes back, then send it. If it comes back slightly wrong, so much the better — watching it get fixed in one plain sentence teaches more than watching it work first time.

Worked in the room: Labs 1–3.

Sent home: Lab 4 is a week of real use, then sharpening the file. Say plainly that it is the homework and that it is the one that compounds.

#007 — Breadcrumbs

Demo: break a file on purpose and get it back, on the screen, before they do it. This is the one people are frightened of and the one that stops the fear.

Worked in the room: Labs 1 and 2 — git installed, one marker, break it, ride back.

First to go: Lab 3, GitHub, needs an account and an email confirmation and it will cost you fifteen minutes you may not have. It is written down. Let it go home.

Ask for a volunteer at #003

One real business, built on the screen, from the folder stage onward. Their facts, their phone number, their “we don’t do gas”. The more ordinary the trade, the better — a septic service or a fence contractor beats a photographer, because a page that works for those works for anybody watching.

Every instruction you type then has a real reason behind it instead of being a demo about an invented bakery, and the volunteer goes home with a working page for a working business.

Ask two things first: whether they are happy for it to stay up afterwards, and whether you can point at it when somebody asks what one of these days produces. No to either is a perfectly good answer and changes nothing.

04Running late

Cut in this order. Do not speed up — the day is already at the pace people can follow.

Cut	Buys	What is lost
1. #007 Lab 3 — GitHub	15 min	Nothing today. It is on the page and it needs no help.
2. #002 Lab 4 — pick your first job	15 min	Little. Fold it into the closing sentence at 16:25 instead.
3. #006 Lab 3 — hand it a real job	15 min	Some. #005 Lab 3 already made the point; this one deepens it.
4. #001 Lab 4 — the privacy setting	5 min	Say it from the front instead. Thirty seconds, and do not skip it silently.
5. #007 entirely	40 min	Real. Say so: “we did not get to the undo, and it is the one that makes the rest safe. It is workshop seven on the site and it is an hour.”

Never cut #003 or #004. The folder and the editor are what everything after them stands on. A day that ends at #005 with a folder made properly beats a day that touched all seven and left half the room without one.

05Before anybody arrives

Most of a day going well is decided before the first person sits down.

Ask the host, before agreeing a date

What is the wifi actually like with twelve people on it? Not “do you have wifi”. This is the one real risk of the day and it is worth being blunt about.
Is there a screen, and what does it take? HDMI, USB-C, or an adapter you need to bring.
Power at the tables. Six hours of laptops. Bring a power strip regardless.
Room layout. Tables, not rows — people need to see each other’s screens.
Can you get in early? Thirty minutes before the first arrival, not five.

Send with the confirmation

Everything on the site’s short-trail page already says this, so send that link. The four that matter:

A laptop they can install things on — not a tablet, and not a locked work laptop. The one item you cannot fix in the room.
A charger.
Free account at claude.ai or chatgpt.com, made in advance.
The facts about their business — phone number, hours, area, what they do not do. They build a real page from these.

On the morning

Your own machine on the projector, text size up two steps — the A+ button on every page.
setup.html open in a tab. It is the page you will point at all day.
Dale’s files open at #003 chapter one, for anybody who arrives with nothing of their own.
Download the VS Code installer before the room fills. Twelve people downloading it at once over a library connection is how you lose the morning.
Phone hotspot on, tested, as the fallback for your own machine.

06When it goes wrong

All of this has happened. None of it needs anything clever.

What you see	What to do
The room’s wifi collapses	Honestly: this day needs internet and there is no offline version of it. Switch to your own screen on the hotspot and keep going — every lab is written down on the site so they can do it at home. It is the one real risk, which is why you ask a host about the wifi before agreeing a date.
Twenty minutes behind at lunch	Do not speed up. Go to the cut list and take the first two. Tell the room you are dropping them and where they are written down; a room forgives a cut it was told about and resents being rushed.
A work laptop with no administrator password	No fix in the room. Pair them with a neighbour and make sure they watch every install step. Say plainly that it works on their own machine at home.
VS Code asks whether they trust the authors	Yes. It is their own empty folder and they are the author. Say it before it appears.
`claude` is not recognised	The terminal was open before the install finished. Close it, open a new one.
No Source Control options in VS Code	Git was installed while VS Code was running. Fully close it and reopen.
“Claude Code requires a paid plan”	Expected. Free accounts do not open it. Switch them to the browser route and carry on — do not spend room time on a billing page.
Somebody is lost and will not say so	They always exist. Walk the room at the start of every lab rather than asking “everyone alright?” from the front, which reliably gets you nods.

07If it is two days

All twelve fit across two, comfortably, with the second day doing the part that pays.

	Covers	What they leave with
Day one	#001–#007	A folder, an editor, an assistant working in it, house rules written down, and an undo behind all of it.
Day two	#008–#012	A brief, something built from it, a database if they need one, a live web address, checks that run themselves, and a sign-in if anybody else has to get in.

Day two is the one people talk about afterwards, because it ends with an address they can text to somebody. If a host can only take one day, do day one — without the folder and the undo, day two builds on sand.

The gap between the two days is the point A week or two apart beats back-to-back. #006 sends them away to use it on real work for a week and then sharpen the instructions file, and that week is where the habit forms. They come back to day two with real questions instead of hypothetical ones.

08The short version instead

When a day is not on offer.

The short trail is the whole thing pressed into 120 minutes — eight stops, six labs, and everybody still leaves with a live address. It is a different promise, not a smaller one: it goes wide and shallow where the day goes deep.

Use the day when a host can give you one and the group is committed. Use the two hours for a library evening, a chamber of commerce, or anywhere people have turned up to find out whether this is for them at all.

09The Code Dungeon session

A different session: one screen, one presenter, and nobody in the room installs anything.

The page is code-dungeon.html. The session runs about 45 minutes: roughly 30 of you walking round the dungeon on the projector, then questions. Nobody installs anything in the room. Demo mode is on the page, under Try it at home, so anybody can run what they watched at their own desk.

Code Dungeon — about 45 minutes

Demo: all of it, on the projector, in the order of the page’s parts. What is on the screen is the demo: pretend projects and pretend coders. Nothing touches GitHub and nothing uses your subscription.

Worked in the room: nothing. Parts VI and VII, Install it and Your first project, stay on the page. Don’t install anything live.

The moment: part III, one job start to finish. File a short issue on the notice board, say Add a contact page, and let the room watch a coder pick it up at the bench and a tester check it in the assay room.

Part	Minutes	Where
Setup	15	Before anybody sits down. The list below.
I What Code Dungeon is	5	The page first, then the great hall.
II Who’s who	6	The great hall.
III One job, start to finish	10	Through the archway into a chamber. The beat of the session.
IV What you need	2	The page. No dungeon.
V Try it at home	2	The page.
VI–VII Install it, Your first project	3	The page, and one last trip to the recruits’ chairs.
VIII When something goes wrong	1	The page.
Before questions	1	The cat and the dart board.
Questions	about 15	Leave the dungeon on the screen.

Before anybody arrives

15 minutes before the session, open PowerShell in demo-code-dungeon and run powershell -File start.ps1.
Three green OK lines, then wait for the green line Ready: the demo is at http://localhost:4400. The first run of the day can take a few minutes, because it downloads Code Dungeon.
The browser opens on the start screen. It says DEMO MODE: fake repos, fake coders. Press Enter the dungeon.
Before the projector goes on, check two things: the badge at the top right says DEMO, and the address bar says localhost:4400. Not 4417.
code-dungeon.html open in another tab. The session goes back and forth between the two.
Leave the PowerShell window open behind the browser for the whole session. Closing it stops the demo.
Sound off before people arrive, unless you want the music: M turns all sound on or off, N just the music.

Port 4417 never goes on the screen. That is your real dungeon, and it shows client names. If it is up, or the DEMO badge is missing: projector off first, then fix it.

Afterwards

Click into the PowerShell window and press Ctrl+C. It says The demo has stopped.
Windows asks Terminate batch job (Y/N)?. Press Y, then Enter.

The runbook

The running order part by part, the keys, and what to do when it goes wrong are in demo-code-dungeon/RUNBOOK-code-dungeon.md, next to start.ps1. It is presenter material and is not on the website. Three rows from it worth knowing without looking:

What you see	What to do
The wrong dungeon on the screen — no DEMO badge, the address says 4417, or a client’s name	Projector off, or switch the input, first. Then close that tab. Type `localhost:4400` yourself, check the start screen says DEMO MODE, press Enter the dungeon, check the badge says DEMO, and only then put it back on.
`WARNING: ... it is NOT the demo`	Do not put it on the projector. Press Ctrl+C, answer Y, and run `start.ps1` again.
`Not ready after 5 minutes.`	Check the internet is on: the first run downloads Code Dungeon. Look up the window for an error in red. Press Ctrl+C, answer Y, run `start.ps1` again. Still nothing: teach from the page. The two drawings carry parts II and III without the dungeon.

10Before Tacking Up

The thirty-minute introduction: one screen, everybody on their own laptop or phone, nothing to install.

The page is Tacking Up. I run it straight down the page, in this order. It adds up to 29 minutes, which leaves one for somebody’s login.

Part	Minutes
Before we start	2
01 The horse in the field	5
02 Putting the tack on	7
03 The ride	7
04 Words back, or work done	5
05 Now ask it about your business	3
Total	29

Before anybody arrives

A paid Claude account, signed in, on your own machine.
The Claude desktop app open. Folders on your computer need the desktop app; the table in chapter 04 says so.
An empty folder called saturday, ready to connect for the chapter 04 demo.
Approvals on Manual, so it asks before it saves anything.

Free accounts get a limited number of messages every five hours. Anybody who hits the limit watches the screen and tries the last two prompts at home. Anthropic explains the limit at support.claude.com/en/articles/10684626.

Run sheet · a day with the twelve