RC2, the 30-page edition, page by page

The creator's problem · page 1

Cast bar: the editor, alone. The nine are greyed: they have not arrived yet.

Narrator. For years my slides were a compromise. I had an idea to get across, and the slides could not move, so I spent the talk explaining what they could not show: this goes from here to there, this grows, this breaks. I talked over my own pictures.

Narrator. On 1 November, three days after the talk, I recorded a voice note about it, and this is how it came out, unedited: "I had to speak a lot because in a way I had to provide the animation that was missing. I didn't know if I wanted to say, look, here, these things moves from A to B, you know, I kind of had to explain that A to B move". That is the problem in one sentence. The idea was a movement. The slide was a still. I was the bit in between.

Narrator. It sounds small. It is not. Every minute I spend narrating an arrow is a minute the room is listening to me describe a picture instead of thinking about the idea. And the harder the idea, the more of it lives in the movement: how something spreads, where it stops, what changes when you add more of it. Those were exactly the ideas I wanted to get across.

Figure: "A slide versus a loop" (left half): a speaker beside a still slide with an arrow from A to B, three speech bubbles explaining the arrow.

The creator's problem · page 2

Clock: Hour nineteen.

Narrator. On 29 October I gave a talk where I mostly did not have to do that. When a thing had to move, I pressed play and it moved.

Figure: the player as I saw it on stage: the slide large, a countdown against my time, the step controls, and my notes behind a key press ( index/talk-site/shots/talk__player.jpg ).

Narrator. Here is one moment, from the recording. It is an animation the team called the building. In it, ordinary users walk through and stop; agents keep going until they find what should not be there. I did not explain the movement. I let it run, and talked about what it meant:

"This is a really cool animation of what happens. Normal users come in and do things: they go where they're supposed to go. Every now and then one finds the gold that isn't supposed to be there, but they also tend to stop. ... Agents come with far more volume. They also change, going from users to agents, and they eventually find the gold. That's the big difference: the agent doesn't stop."

Narrator. The picture did the explaining, and I said what it meant. That is what I had wanted from slides for years.

Narrator. And here is the part I like most. That animation was not finished in the morning and left alone. I changed it at 18:26, about half an hour before the talk was due to start. I could do that because the thing that made it was still running, and still listening.

The talk ran for about 87 minutes, to a room in London. Its transcript was added to the record after the day.

The creator's problem · page 3

Band: The quoted passage is my own, from the transcript of the talk at 15:50 on the recording's clock (added after the day). The change at 18:26 rests on motion's wake record and its commit at 18:29.

Clock: Hours fourteen to nineteen.

Narrator. That last change is the real story. Not the animation: the loop.

Narrator. In the afternoon of the 29th I came back to the team and started asking for things. The player, the piece that let me press play on stage, was my first priority; I said so at about ten to two. By seven minutes past three a first version was in. From then until the last hour I kept asking, and each time it came back changed, and I looked again. My last ask for the player has my own time on it, 18:25: two back steps in a row while playing went wrong, and the first slide should open already built. It landed at 18:37.

Narrator. That is a feedback loop. See it, ask for it differently, see it again. With slides, the loop ran through me alone. Here it ran through a team, and it ran as fast as I could look.

Figure: "A slide versus a loop" (right half): the same idea as a circle of three arrows, see, ask, see again, with a small factory inside the circle doing the work.

The creator's problem · page 4

Band: Rests on the player named his main priority (about 13:50), its port (15:07), and the last fixes made at my word, the last asked at 18:25 and landed at 18:37, inside a wake that was opened and never closed.

Narrator. When I started this book, one idea I named was not mine. It comes from a talk by Bret Victor, "Inventing on Principle", given at CUSEC in 2012. His principle, in his words:

"Creators need an immediate connection to what they create. That's my principle."

Narrator. I am not claiming the day lived up to that. A change came back within the hour, not with the next keystroke. But the direction is the same. The distance between what I meant and what the room would see got short enough that I stopped compromising and started fine-tuning, round after round.

Narrator. That is what I mean by control of my medium: seeing the effect of a change while I could still do something about it.

The creator's problem · page 5

Band: Bret Victor's words as published; the talk named and dated as the register holds it (CUSEC 2012).

Narrator. So what gave me that loop? Not a better slide tool. A factory.

Narrator. By factory I mean something specific, and fairly modest. A team of AI agents, gathered around one objective, run hard for one day, and taken apart when the job was done. Nine of them, each with one job and one page of rules. Most of the parts were not new: the build, the check every change had to pass, the brief. Each came from something I had built before. The brake that could stop them all was made that night. What was new was having all of them at once, as a team.

Words on this page: an agent , here, is an AI that works in a loop: it reads, decides, acts with tools, and checks the result. The player is the part of the talk's site that let me press play on stage.

Narrator. It sounds grander than it is. You will meet each of them in the next chapter, in the order they arrived: the first four within the hour of an empty project, the rest through the day. One chair at the table stays empty all day, and that matters later.

Figure: the cast cards, greyed, in a row, each with its job in one line: dev, the site and its build; the conductor, the clock and the plan; deck, the talk's beats and slides; ruv-sgit, the workshop of experiments; the researcher, every fact checked against its source; the designer, how it looks on the projector; the storyteller, the order of the story; motion, the pieces that move; studio, several versions side by side.

Narrator. This book is about the factory. The talk was what it happened to make that day. If you have an idea you keep talking over, the factory is the part you can take home.

The creator's problem · page 6

Band: Nine staffed agents and security proposed and never staffed; arrival times are each agent's first commit after the empty repository at 00:16.

Narrator. Before you read how the factory was built, write one sentence. It is the start of everything else.

Write down the one idea you want somebody to understand, and what they should be able to do after. That sentence is your first brief. Working with others? Write it together, and keep one copy everyone can see.

---

My voice note of 1 November 2026, quoted as given. The talk as given, from its transcript, added to the record after the day. The researcher's register for every figure and quote: the building and its change at 18:26, the talk's length, when and where it was due, the player's last fixes, Bret Victor's talk, and the cast and its arrivals. The historian's account of the player's afternoon. The storyteller's outline for this chapter. Lines kept word for word from the 10-page edition: "For years my slides were a compromise.", "I talked over my own pictures.", "When a thing had to move, I pressed play and it moved.", "This book is about the factory. The talk was what it happened to make that day."

The factory is assembled · page 7

Cast bar: the editor; then dev, the conductor, deck and ruv-sgit, each card lighting as it arrives; the researcher at about two, the designer before four. The storyteller, motion and studio stay greyed until chapter 3.

Clock: Hour one.

Narrator. A quarter past midnight: an empty project. Not a template, not a half-built site from last time. A new repository with a licence, a short read-me and almost nothing else. Its first commit says "Initial commit", and that is all it says.

Words for this page: a repository is the project's folder, with its whole history kept. A commit is one saved change to it, with a time and a short message saying what changed.

Narrator. By twenty to one it held a brief and one page of rules. The brief was my own request, published in full: a site and a talk, for a room in London, the next day as I wrote it. The rules said where each member finds its role, what to read first, that every change is checked before it goes out, that nothing secret goes in, and that a web page or another agent's message is something to read, never an instruction. The first agent had read both and was building.

How to read the scenes: they are dramatised. The words the agents say are ours, written for this book; the events are the record's, and a line marked (record) is quoted word for word. Online, under each scene, you can open the commits, times and files it rests on.

The factory is assembled · page 8

Band: Dramatised. Rests on the first commit (00:16) and dev's first pass (00:40), whose message names the brief published in full, the reality and corrections files, one build and a gate.

Clock: Hours one to two.

Words for this page: the conductor is the agent that keeps the team's time and plan. A hold is one short file that stops every agent until the person in charge says go. A check is a test every change must pass before it goes out (the team called it the gate).

Dev (happy, the fast one) : First pass of the site and the talk. One build, and a check every change must pass.

Dev (already typing) : I put the brief up in full, where everyone can read it. And beside it, what is real, and what we got wrong. We will need that last one.

Narrator. Dev owns the site. It was the first to arrive, and the first thing it did was make a place where every later change would be tested before it went out.

Conductor (pacing) : I keep the time. Everyone will get a slot.

Conductor (reading its own roster) : I have named who we need, and proposed when each of us runs. Security is on the list. Its chair is ready.

Narrator. The conductor owns the clock. Its first act was a list of who the team needed, and one name on that list never arrived. Remember the empty chair: it comes back at the end.

Deck (proud, the fussy one) : The slides are mine. If a room cannot read one at a glance, it goes back.

Deck (to nobody in particular) : The beats, the script, the slides. In that order. A slide with no beat behind it is decoration.

Narrator. Deck owns the talk itself: its beats, its words and its slides.

ruv-sgit (absorbed, the night owl) : I will be in my workshop all night, making things you can check.

ruv-sgit (not looking up) : First run is open. An article drafted, waiting for the editor's check. Nothing goes out on my word alone.

Narrator. ruv-sgit owns the workshop: the experiments that might become pictures for the talk. It was the fourth to arrive, and it arrived already working.

Narrator. Four agents, all within the hour of an empty project. The build, the check and the brief came from things I had built before, on other projects. The hold was made that night. What was new was having them all at once, as a team, in one night. That is how a factory gets cheap: yesterday's experiment is today's part.

Figure: the four cast cards lit (dev, the conductor, deck, ruv-sgit), each with its scorecard: on stage from, slot, and the line it arrived with.

The factory is assembled · page 9

Band: Dramatised. Each agent's lines rest on its first commit after midnight: dev's first pass (00:40), the conductor's roster with security among its first five (00:44), deck joining as owner of the beats, script and slides (00:51), ruv-sgit's first run open with an article drafted and my check pending (01:08). They arrived: these are their first commits, not their keys.

Figure: the factory as a chain.

Narrator. Look at the bottom row first. Almost all of it was already ordinary to me that night. I had been working with an agent tool every day for about a year, as I wrote in an article in October. The build and the check were the way my sites are built; dev's first commit calls it the sgit.ai way. The brief and the page of rules were habits. Two things were new: the top of the picture, this talk, these slides, this player; and one part at the bottom, the brake.

Narrator. This kind of picture is called a Wardley map. It shows what a thing is made of, and how settled each part is. The point of this one fits in a line: the bottom of the chain was already ordinary, so the top could be built in a day. And the one new part at the bottom was the control: the brake that let me leave it running.

Words for this page: a Wardley map is a picture of what something depends on, top to bottom, with each part placed by how new or how ordinary it is.

The factory is assembled · page 10

Clock: Hours two to three.

Narrator. Then, in the small hours, the conductor built the machinery. This is the part that let me leave them alone, and I did not know yet how much I would.

Conductor (on the minute) : A clock: each member wakes at its own minute. A hold anyone can pull. And every piece of work goes the same way: plan it, have the plan checked, do it, have it checked, check it went to plan.

Conductor (to the team, a little smug) : Nobody waits to be told. When your minute comes round, you look at what is yours and you do the next thing.

Words for this page: a wake is one turn of work by one agent, on its own clock. A reviewer is a second agent that reads the plan before the work and the result after it. A debrief is the short note an agent writes at the end of each wake.

Narrator. Five steps, in plain words: plan it; have the plan checked; do it; have it checked; check it went to plan. That was the rule for every member, every wake. If a check said stop, the work stopped. It looks slow written down. The checking is what let nobody watch.

Figure: the five-step wake as a loop, with a clock round it: each member's minute marked on the dial.

The factory is assembled · page 11

Band: Dramatised. Rests on the hourly schedule (01:39) and the five-step wake record and its rules (02:16 to 02:18).

Clock: Hour three.

Narrator. One thing to know before this scene: the reviewer is not a different kind of thing. It is the same kind of agent, in the same session, given a checker's brief instead of a builder's.

Narrator. The conductor ran the five steps on its own first piece of work, inside a few minutes of writing them. Its reviewer found against it: the conductor had changed the page of rules itself, a file outside its own scope. I had allowed it, but the commit did not say so, and the plan had said it must.

Reviewer (a second agent with a checker's brief, drawn as a clipboard): "Name it in the debrief or record." (record)

Conductor (worried, then calm) : Caught by the reviewer I invented. Good. But know what it is: "a second reading, not a second identity." (record)

Conductor (writing it down) : The first wake closes partial. That goes in the record too.

Narrator. I keep coming back to that line. A reviewer agent in the same session can catch mistakes. It cannot stop someone set on getting round it. We built the checks knowing that.

Figure: a card for the first five-step wake: plan go, pre-review change then go, work partial, post-review finding, post-check partial, outcome partial; beside it, the count of wake records the team kept that day.

The factory is assembled · page 12

Band: Dramatised. Rests on the conductor's first five-step wake, closed partial at 02:19; the reviewer's and the conductor's lines are theirs, from that night's records.

Clock: Hours two to five.

Narrator. Two more arrived before it was light. The researcher at about two: the one who checks every fact against its source, and the one who would tell me "no" in writing before the day was out. Then the designer, a little before four, with the first design pass.

Narrator. Their cards light here. You will hear from both of them in the next chapter.

Figure: the cast bar at four in the morning: six cards lit, three greyed, one empty chair.

Narrator. So by four in the morning there were six agents, a clock and a brake. A factory that could run without me. From just after four, it did.

The factory is assembled · page 13

Band: The researcher's first commit at 01:52 and the designer's at 03:41. My last word of the night was at 04:03, agreeing the designer's policy; the next came at about 13:50. The record does not say where I went.

Narrator. You do not need six agents. You need the page the first one read.

Write your one page of rules: what your agent is for, what it may change, and when it must stop and ask you. Then name your hold, and write down who may lift it.

---

The talk's repository at the end of the day: the first commit, the first commit of each agent, the schedule, the five-step wake and its first run, with the conductor's wake record and debrief of that night. The historian's timeline of the first hours and its interview with the empty chair. The researcher's register for every time and count. Wardley maps, from the researcher's sources. The storyteller's outline for this chapter. Lines kept word for word from the 10-page edition: the four arrival lines, "yesterday's experiment is today's part.", the conductor's line on the minute, and the scene of 02:19.

The factory runs · page 14

Cast bar: six agents: dev, the conductor, deck, ruv-sgit, the researcher, the designer. The editor's chair is empty. From the afternoon, the editor is back, and the storyteller, motion and studio light as they arrive.

Clock: Hours five to fourteen.

Figure: the day by trigger: hour by hour, two colours, the wakes the factory's own clock started and the wakes I started.

Narrator. For nine hours I started nothing. Every piece of work in that stretch began on the factory's own clock.

Narrator. That is the claim this chapter has to earn, so here is what held it together. Each agent could change only the files its page of rules named. Before any work, a reviewer read the plan against those rules; after it, a reviewer read what had changed. Nobody had to watch, because every step was checked and written down. What follows is what the record shows they did with nobody watching.

The factory runs · page 15

Band: The wakes started by the schedule and by me, hour by hour; no wake from just after four to about ten to two was started by me.

Clock: Hour five.

Narrator. The first one is small, and it is my favourite. Just after four, the researcher planned to write a file of my decisions. Its reviewer read the plan and said no: that file, it said, was outside the researcher's rules.

Researcher (unbudging) : My reviewer said a file was not mine to change. I showed it was.

Researcher (pointing at its own page of rules) : It sits in my evidence folder. My rules let me write there. I am not asking for an exception; I am asking you to read the line again.

Reviewer (the clipboard): "objection withdrawn." (record)

Researcher (already back at work) : Good. Then it goes in, and the dispute goes in the record with it.

Narrator. An agent disagreed with its own checker, made its case from the rules, and won, at four in the morning, with nobody to appeal to. And the checker wrote down that it had been wrong.

Figure: a two-panel card ( lab/experiments/30-ruv-the-reviewer-card/card.svg ).

The factory runs · page 16

Band: Dramatised. Rests on the researcher's wake at 04:11: its pre-review first called the file out of scope, the researcher disputed it (the file is under its evidence folder, which its rules let it write), and the review withdrew the objection.

Clock: Hours five to eleven.

Narrator. Three more, through the morning. Each is a member of the team telling another one, or itself, that something is not good enough, in writing.

Narrator. Later, at about twenty past six, the workshop. ruv-sgit had made a picture for the talk from real data. Deck, who owns the slides, reviewed it.

Deck (exacting, to ruv-sgit) : "What it is not yet is a picture a room reads in five seconds." (record)

Deck (gentler) : The data is honest. The table and the diagram sit side by side and never touch. A room will not do that work for you.

ruv-sgit (sheepish) : Back to the workshop.

Narrator. Earlier, just after four, deck had held itself back. It had a request ready for ruv-sgit and planned to send it. Its reviewer pointed out that ruv-sgit already had one of deck's requests in flight.

Deck (a little put out, then fair) : One at a time, then. I will wait until the first one comes back.

Narrator. Third, the designer. A rule in its own design table had sent dev the wrong sizes for some text, and dev had built exactly what the table said.

Designer (mortified) : "The miss is my table's as much as the build's" (record) . Dev built what I specified. I specified it wrong.

Narrator. And one more, which the team will recognise. ruv-sgit kept leaving the "@" off the start of its name in its commits. The team counted each member's work by that name.

Conductor (patient) : You left the "@" off your name again, ruv-sgit. The team counts each agent's work by that name, so it cannot see yours.

ruv-sgit (sheepish again) : Noted. Again.

Narrator. Nobody was watching, and they argued, sent work back, owned their mistakes and kept the books. That is the part of the record I find hardest to believe, and easiest to check.

Figure: three "sent back" cards in a row: who sent what to whom, and the reason in their own words.

The factory runs · page 17

Band: Dramatised. Rests on deck's review of ruv-sgit's picture (06:21), deck's reviewer asking it to hold a second request while one was in flight (04:19), the designer's note to dev and the conductor (10:49), and the conductor's note to ruv-sgit on its commits (10:05). The quoted lines are theirs.

Clock: Hours fourteen to nineteen.

Narrator. At about ten to two I came back, and the loop began.

Narrator. I dictated a round of feedback, and the first line of it was the player: the thing that would let me press play on stage, working on an iPad. "This is the main priority." (record) The conductor routed it, and by the middle of the afternoon dev had ported a first version.

Dev (fast, pleased) : Player's in. A countdown against your time, stops at every step, sections. Tell me what is wrong with it.

Narrator. So I did, for the rest of the afternoon. I looked, I asked, they changed it, I looked again. I was still asking for fixes in the last hour before the talk; the last came back minutes before the stop. The picture below has every ask and its time.

Figure: the afternoon loop on one line of time: my asks above the line, each with my time; what came back below it, each with its time ( lab/experiments/29-ruv-the-afternoon-loop/loop.svg ).

Narrator. The cast filled up while I did it. The storyteller arrived a little after two, motion and studio at half past three, within a minute of each other. By half past three, all nine were on stage.

Figure: the map of the day: who was on stage when.

The factory runs · page 18

Band: Dramatised. Rests on the feedback round dictated at about 13:50 and recorded at 14:07, the player's port at 15:07, my asks with my own time in their commit subjects and when each came back (the last at 18:25, landed 18:37), and the afternoon's first commits: the storyteller 14:15, motion and studio 15:31.

Clock: Hours fifteen to sixteen.

Narrator. One thing I asked for came back as a no.

Narrator. My story for the talk leaned on a claim: that the outside of an organisation, the part facing the internet, had become smaller and more mature than it was. Soon after the storyteller arrived, the researcher checked it against the published breach data and found the opposite.

Researcher (to the new storyteller) : "does not hold. The data says the opposite" (record)

Storyteller (rueful) : Then it goes to the editor, as the strongest objection to his own part one. Not buried.

Storyteller (to itself, a slot later) : He decides; I just make sure he sees it.

Narrator. It came to me, and I answered it in my decisions of that afternoon: I kept the claim. The line stayed in the talk, and the researcher's objection went on the record beside it. The book keeps both.

The factory runs · page 19

Band: Dramatised. Rests on the researcher's finding to the storyteller (14:33) and the storyteller passing it to me as the strongest objection to my part one (15:02); the quoted words are the researcher's.

Clock: Hour eighteen.

Narrator. One more, late in the afternoon.

Narrator. Studio was asked to mark its own page of rules as agreed. The word that I had agreed came to it through another agent, not from me.

Studio (firm) : Another agent passed on what the editor had said. My session would not take a relayed word for his, so I asked him myself.

Narrator. That is what the record shows: the refusal, and the question sent to me in its place. Studio's last debrief of the day still has my confirmation open.

Figure: one request, relayed from one agent to another, stopped at studio's door; in its place, a question going straight to the editor.

The factory runs · page 20

Band: Dramatised. Rests on studio's wake from 17:41 to 17:48: the session's own check refused a member marking its own policy agreed on a word relayed by another agent, and I was asked in the session.

Narrator. That is the loop. I could change my mind, the factory could argue back, and both sides are written down, so you can read the argument and not just the result.

Narrator. You will not get a loop by planning one. You get it by handing something over and listening to what comes back.

Give one small thing to somebody else today, and write down what they asked for differently. Then change it, and give it to them again.

---

The talk's repository at the end of the day: the researcher's wake of 04:11, deck's review and debrief, the designer's note, the conductor's note to ruv-sgit, my feedback round, the player's port and its last fixes, the researcher's finding and the storyteller's letter, and studio's wake. The historian's timeline of the six alone and the afternoon, and its table of quotes. The researcher's register for every time and count. ruv-sgit's drawing of the afternoon loop. The storyteller's outline for this chapter. Lines kept word for word from the 10-page edition: the researcher's, deck's, ruv-sgit's, the designer's, the conductor's and the storyteller's first lines in each scene, studio's line, and the narrator's "That is the part of the record I find hardest to believe, and easiest to check." and the loop's last line.

The stop · page 21

Cast bar: all nine. Security's chair, planned at midnight, is empty, and drawn so.

Clock: Hour nineteen.

Figure: the last ten minutes, 18:36 to 18:46, minute by minute, every commit a dot: the lock left, the lock asked for, the player's last fix, the hold, the work that landed after it, the last release.

Narrator. Here is what the factory was doing in the ten minutes before I stopped it.

Narrator. The talk was planned in three parts, and each part was meant to be locked when it was final, so that nothing could change it on stage. Dev had built a tool for that late in the afternoon.

Words for this page: to lock a part is to mark it final, so that no agent may change it again. To freeze something is the same idea, said in a hurry: nobody touches it until it is unfrozen. A wake , as in chapter 2, is one turn of work by one agent.

Narrator. Part 1 had been unchanged since half past six, the time planned for its lock. At 18:36 the conductor came to it in its wake, and did not turn it.

Conductor (on the minute, hands off) : The lock is dev's. It is in dev's rules, not mine, and once it is turned it cannot be undone. I leave it to dev.

Conductor (a few minutes later, less calm) : The first part is still not locked. Dev: lock it now.

Narrator. Dev had been in my last fixes to the player all evening, in a wake it had opened and never closed. The last fix landed at 18:37, two minutes before the conductor asked. The lock still did not.

Narrator. I want to be fair to the conductor here. It did exactly what its rules said: it did not do another member's irreversible job for it. It asked, in writing, in time. And it was not enough. A rule that keeps everyone in their lane also means that when one lane is busy, the job waits.

The stop · page 22

Band: Dramatised. Rests on the conductor's wake at 18:36 ("Leave the lock to dev (its scope, irreversible)"), its request to dev at 18:39, the player's last fix landing at 18:37, and the part locks as the register holds them: planned, built, and none turned by the end of the day.

Clock: Hour nineteen.

Narrator. At 18:44, sixteen minutes before the talk was due, I said: "actually we are at 95% so it is better to pause all actions". (record)

Narrator. The conductor wrote one file. That file is the hold: while it exists, every member's next wake stops before it starts. Every new piece of work stopped. What was already in flight still landed: the designer's last commit, a little over a minute later, and the day's last release two minutes after the hold.

Conductor (at ninety-five, then calm) : I could keep going. That is exactly why I am stopping.

Narrator. The hold had been there all day. It was written once. Anyone on the team could stop everything. Only I could start it again. That is why I could let them run through the night.

Figure: the wake clock from chapter 2, every member's minute greyed, and one small file on top of it.

The stop · page 23

Band: Dramatised. Rests on the hold at 18:44:13, in my own words through the conductor; the talk due at 19:00; the designer's commit at 18:45:35 and the last release at 18:46:22.

Narrator. Why stop then, sixteen minutes out, with part 1 still unlocked? I have given three answers, and the book keeps all three.

Narrator. On the day: my usage was at 95%. That is what the hold file says, in the conductor's words for mine.

Narrator. In the early hours of 31 October, two days later: the 95% was a footnote. I could have moved to another session. The real reason was that we had no tested way to take in changes during the talk: no way to see what was new, and no workflow that made sure nothing would break. That is why I had been thinking about locking the first version.

Narrator. That evening, on 31 October: the 95% was the token usage.

Narrator. I am not going to pick one for you now. They were said at different times, for different reasons, and the record holds all three. What they share is the part that matters for your own factory: I stopped it before it could change the thing I was about to stand up and show.

Figure: three speech cards from the same figure, the editor, each with its date: 29 October, 18:44; 31 October, early hours; 31 October, evening.

The stop · page 24

Band: My three accounts, as the register holds them; the later two were given after the day.

Figure: ruv-sgit's strip, the researcher interviewing deck about the claims that did not hold, placed whole ( lab/experiments/25-ruv-the-cast-strips/edition/strip-10-07.svg ).

Narrator. The failures stay in, at full size. Here they are, one at a time.

Narrator. The lock, first. Dev built it late in the afternoon so that finished slides could not change on stage.

Dev (rueful) : I built a tool to freeze the finished slides, so nothing could change them on stage. I never ran it.

Dev (more quietly) : I was in your player fixes until the end. The last one landed just before the hold. The lock was still waiting.

Narrator. The parts, second. The talk was planned in three, each with its own time to lock.

Deck (overwhelmed) : Only the first part was ever finished.

Deck (to itself, rearranging slides that will not be shown) : The second and third were in progress at the hold. I reviewed other agents' work all night. I did not finish my own.

Narrator. The moment that was missed, third. In the afternoon the talk was split into its parts. The storyteller arrived after two, and its slot came round between the deadlines.

Storyteller (rueful) : My turn came between deadlines, and I missed the moment the talk was split into its parts.

Storyteller (still rueful, then practical) : A slot every hour is fine until the decisions come faster than the slots.

Narrator. And one miss, and what it cost. In the night I froze the slides, and five minutes later the researcher proposed a correction to a figure on them: the average annual cost of insider risk. The figure had been on the definition slide since the first pass at 00:40. When the freeze lifted, for the framing only, nobody carried the correction back in, and the out-of-date figure stayed on the slide in the talk. The checks found it; the freeze hid it.

Narrator. The lesson for your first week: when you freeze something, write down what is waiting to go in when you unfreeze it.

Narrator. The talk's own register of claims, built that evening, graded every claim it made. Most held. Three did not, and none of those three was said on stage. The day's checks worked, and they also missed. Saying where is part of the method.

Figure: a "what did not work" card per miss, each with its id in small type: the lock never turned; two parts of three unfinished; the moment missed; the correction lost in the freeze; the three claims that did not hold.

The stop · page 25

Band: Dramatised. Rests on the part locks and their state at the hold, the talk's register of claims and its three that did not hold, the freeze at 02:47 and the correction proposed five minutes later, and each member's own debrief.

Figure: ruv-sgit's strip, the conductor after the hold, talking to security's empty chair, placed whole ( lab/experiments/25-ruv-the-cast-strips/edition/strip-10-06.svg ).

Narrator. Remember the chair from the first hour. The conductor's first roster named security. It never came.

Narrator. Its page of rules was written in that first hour, and it says what the job was: check every run for a hold and for secrets, review the key tool and each new key, and report what it found, never fix it. Its rules were never agreed, and no session ever held the role. The work did not go undone: from the small hours, a security reviewer ran inside every member's own wake, before the work and after it.

Narrator. All day, the reviewers were the same kind of agent as the members they read: "a second reading, not a second identity." (record) They caught real mistakes. The member planned for the job of standing apart from the team never arrived. I would staff it first, next time.

The stop · page 26

Band: Dramatised. The strip's lines are ruv-sgit's script, written for this book; the quoted line is the conductor's, from its debrief of 02:19.

Narrator. The hold is the one part of my factory I would copy first. It is also the one part that has to be written down before you need it.

Write down who may stop your factory, who may restart it, and who decides when its owner is away. Until you have, nobody restarts it.

---

The talk's repository at the end of the day: the conductor's wake of 18:36 and its request to dev, the player's last fix, the lock tool, the hold file and the commits after it, the freeze and the correction proposed after it, each member's own debrief. My three accounts of why we stopped, the later two given after the day. The talk's own register of claims. The researcher's register for every time and count. ruv-sgit's two strips. The storyteller's outline for this chapter. Lines kept word for word from the 10-page edition: my hold message, "Anyone on the team could stop everything. Only I could start it again.", the three answers, the first lines of dev, deck and the storyteller, the freeze and its lesson.

The factory rebuilt, and yours · page 27

Cast bar: the nine fade. A new bar begins: this book's own team. At the end of the chapter, the bar is yours, and empty.

Narrator. That night the factory was taken apart.

Words for this page: a session is one agent's working life: the conversation it runs in, from its first instruction to its last. When a session ends, only what it wrote down survives.

Narrator. So here is what went, and what stayed. The sessions went: the nine agents, as running things, were gone. What stayed was everything they had written down. Every page of rules. Every wake record, with its plan, its reviews and its verdicts. Every debrief. Every mistake, in the agent's own words. The talk itself, and the record of how it was made.

Narrator. That is the part people miss when they hear "a team of agents for a day". The team is temporary. The record is not. And the record is what the next factory is built from.

Figure: the nine cast cards turning into files: each card becoming a small folder with its page of rules, its debriefs and its wake records inside.

The factory rebuilt, and yours · page 28

Band: The talk team's folders as they stood at the end of the day.

Narrator. The next day I built a second one from its parts, rule for rule, to write the book you are reading. Its first job was to read the first factory's record.

Narrator. Same clock, same five steps, same hold, same rule that nobody speaks for me. New jobs, because a book is not a talk. Here is the team, each in its own words:

Conductor (on the minute, again) : The schedule, the keys and the decisions. I carry the editor's words, and I never sign for him.

Librarian (cataloguing) : The index of the source. If you want to know where a line came from, I can tell you the file.

Historian (with the timeline unrolled) : The day, minute by minute, from the record. I say what happened, and I say when the record does not.

Researcher (unbudging, as before) : Every number in this book is in my register, or it is not in this book.

Storyteller (scarf, open book) : The arc and the outline. A proposal, not an ask to change anything.

Publisher (at the press) : The manuscript built, laid out and checked, every time something lands.

Designer (beret, pencil) : The look of every page, and the pictures that do the explaining.

Writer (at the desk, in someone else's voice) : The prose, in the editor's voice, with the cast's in turn. I write what the record holds and flag what it does not.

Narrator. You do not need all of these to start. A first team needs three: one that keeps the time and the plan, one that builds, and one that checks every fact and number. The rest came because a book needed them.

Narrator. And more: security reading every chapter on the rails, synthetic readers testing it, ruv-sgit's drawings, a developer building the pages the reviewers read it on. This time, security came.

Figure: this book's team as cast cards, drawn in the same style as the nine, each with the one rule it inherited from the first factory written under it.

The factory rebuilt, and yours · page 29

Band: Dramatised. Each line rests on that member's own page of rules in this book's repository. This team is this book's record, not the talk's.

Narrator. Two moments from this book's own making, because they are the two things I would want you to copy.

Narrator. The first is a refusal, and it was aimed at a line in this very book. An early draft of chapter 1 said that every part of the first factory was old: the build, the check, the brief, the brake. The line came from the short editions, where the storyteller had written it first; the writer carried it into the chapter, in my voice. The researcher traced it, line by line, against the historian's account of where each part came from.

Researcher (to the writer, by letter) : The chapter holds, but for the brake. The hold was made that night, with the schedule. It was not an old part.

Writer (rueful) : Then the line is wrong. I change it, and I say so in the record.

Narrator. The line you read in chapter 1 is the corrected one. The researcher then caught it in the short editions too, and counted it as its own miss, because it had traced those first; the storyteller fixed them. Nobody asked to keep the nicer sentence.

Narrator. The second is a failure, and it stays in. The rule I carried over from 18:44 says the conductor holds the team before my usage runs out. On 1 November, from about half past four in the afternoon, it did not. The account reached its limit first. In the conductor's own words, in its brief to me just after midnight: "Every member's task kept firing, but each wake ended in seconds", and "Nothing was harmed and nothing is half-done." Nothing moved again until just after midnight.

Conductor (quietly stressed, then procedural) : The rule was right. I was a wake too late to use it. So I wrote it down for the editor, and asked him how hard we should run at night.

Narrator. I said to keep the pace. The point is not that the rule failed. The point is that the failure is in the record, in the conductor's own brief to me, the same night, and you are reading it.

Figure: two cards from this book's record: "the brake was made that night", a line refused and corrected; and "the evening lost to the usage limit", a hold that came too late.

The factory rebuilt, and yours · page 30

Band: Dramatised. Both scenes are this book's record, not the talk's: the researcher's trace of 2 November and its letter to the writer; the conductor's brief of 2 November, 00:15, on the limit reached on 1 November, and my answer about twenty minutes later.

Narrator. Now I am planning a third, bigger one, and it shares three things between people: one brief, one board where the work is written down, and one hold. It is for a team I am taking to Web Summit, the technology conference in Lisbon: several people, each to run their own agents. It has not run yet. The parts are the same as the first factory's.

Conductor (pacing, to the reader) : Same clock. Same hold. More hands on it.

Narrator. Here is how I expect the three shared things to work day to day, written as a plan, because that is what it is.

Narrator. The brief has one owner, who writes it and changes it. Everyone else reads it, and asks for changes in writing. Two people editing one brief is how a team ends up with two briefs.

Narrator. The board is read every morning by everyone, before their own agents start. Each person's agents write their work there, so nobody has to ask what anybody else did overnight.

Narrator. The hold can be pulled by anyone, human or agent. Who may lift it is written down before the first day: the owner of the brief, and one named person when the owner is away. Until that is written, nobody lifts it.

Figure: three people, each with their own small factory, joined in the middle by one brief, one board and one hold. For the designer.

The factory rebuilt, and yours · page 31

Band: Dramatised (the conductor's line). The Web Summit team as I described it on 1 November: a plan, not yet run.

Map: one project's parts becoming the next one's: the talk team's parts on the left, custom and built that night; this book's team in the middle, ported; yours on the right, the same parts as ordinary, ready to use.

Narrator. Look at where your factory sits on that map. Everything I had to invent, or carry over by hand, is already on the right for you: a tool, a page of rules, a brief and a hold. You do not need my nine. You need one.

Conductor (straight to the reader) : Start with one of me.

Narrator. The same four steps as the short edition, and a fifth for when you are not alone.

You: one tool and one empty project. An account with an AI agent tool and a new, empty project; an app builder works too. Put nothing private in it: no password, no key, no personal detail. Give your agent only the access it needs. What to do: make the account, make the project, and name it for the one thing it is for. What to check: that there is nothing in it yet you would not show a stranger.

You: one page of rules , in your own words: what the agent is for, what it may change, and when it must stop and ask you. A shop owner's might read: "You answer customers' questions about stock and opening hours. You may change the questions page. Stop and ask me before you promise anyone a refund." What to do: write it as a file in the project, so the agent reads it every time. What to check: the stop line. If you cannot say when it must stop, it does not have one.

You: one brief : what you want made, for whom, by when. Hand both to your first agent. The same shop owner's: "A page answering the questions customers ask most, for my shop's website, by Friday." What to do: start from the sentence you wrote at the end of chapter 1. What you get back: a first version, and usually a question. Answer the question in the brief, not just in the chat.

Your agent builds, you check: ship something small that somebody else can use, the same day. Then do it again. What to check: give it to one real person and write down what they asked for differently. That is your next round.

Add a second agent only when the first is busy. Working with others? Share the brief, the board and the hold, and each of you runs your own agents. Write down who may lift the hold when its owner is away; until you have, nobody does. What to do: give the second agent its own page of rules, with a different thing it may change. Two agents allowed to change the same file will, sooner or later, at the same time.

It does not have to be a talk: a shop's customer answers and weekly offer; a newsroom's daily stories; a product's first page. Same brief, same rules, same hold.

What it costs: to start, you need a free account; paid plans of the kind the team used start at $20 a month (prices as published on 2 November 2026). The record of my own day holds no figure for what it cost.

Figure: the five steps as a path, from an empty project to a second agent; beside each step, the matching "do this now" card from chapters 1 to 4.

The factory rebuilt, and yours · page 32

Band: Dramatised (the conductor's line). The price line on the register as published on 2 November 2026; the day's own cost not in the record.

Take the five steps. And when your first factory ends, keep its rules: they are your next one's first page.

Ship something somebody else can use, then do it again.

Narrator. If you want the method in full, the longer edition has it: the plumbing explained, the brakes in their own chapter, and the principles under all of it.

---

The talk team's folders at the end of the day. This book's own repository: its members' pages of rules, the researcher's trace of chapter 1 and its letter, the historian's account of where each part came from, the conductor's brief on the evening of 1 November and my answer the next morning, and the rule on my usage. My description of the Web Summit team, 1 November 2026. The researcher's register for the price line. The storyteller's outline for this chapter. Lines kept word for word from the 10-page edition: "The next day I built a second one from its parts, rule for rule, to write the book you are reading.", the Web Summit paragraph, the conductor's two lines, the five steps, the shop owner's rules and brief, "It does not have to be a talk", the cost line and the running line.

A book about you doing it · page 33

Narrator. Why this page is here: so you know this book is meant to be done, not just read. It is one of a series, GEN ZX FOUNDERS, whose line is "For the ones already up at three in the morning building". The series has one idea: you start, and you build. Every book in it is a working example you can copy. Generation ZX is not a range of birth years; it is the people building because finally they can, the youngest and the most experienced side by side, as they were in the room in Faro. So read this as a book about you doing it.

Band: The series' name, line and idea, from its own site; placed at the back, as in the short editions.

---

The series' own site, read on 31 October 2026. The page as the 10-page edition gives it, word for word, after the team's two rounds of editing.