# The creator's problem (RC2, the 30-page edition, online) > RC2, the 30-page edition: The creator's problem, with the record each scene rests on. *Source: · site v0.1.383 · generated from the same content as the page, so the two cannot drift.* --- RC2, the 30-page edition, online: under each scene, what it rests on. Made by `review/tools/make_editions.py` from the writer's chapters. # The creator's problem **Cast bar:** the editor, alone. The nine are greyed: they have not arrived yet. ### The old way **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. **Rests on** [`briefs/2026-11-01__in-session/03-the-factory-and-the-zoom.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/briefs/2026-11-01__in-session/03-the-factory-and-the-zoom.md) (the editor's voice note, 1 November 2026, quoted as given) ### Pressing play **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.* **Rests on** [C102](#claim-C102) [C069](#claim-C069) [C100](#claim-C100) [`a9c0b49`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/a9c0b49) [`5d13d72`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/5d13d72) 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.* ### The loop **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. **Rests on** [`c9ced4e`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/c9ced4e) [`3314ffe`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/3314ffe) [`dbd75ad`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/dbd75ad) [C088](#claim-C088) [`timeline/cast-scenes.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/timeline/cast-scenes.md) (scene 5) 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.* ### Inventing on principle **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. **Rests on** [C103](#claim-C103) Band: *Bret Victor's words as published; the talk named and dated as the register holds it (CUSEC 2012).* ### What a factory is **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. **Rests on** [C011](#claim-C011) [C001](#claim-C001) 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.* ### Do this now **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.* --- ### Where this came from 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." **Rests on** [`briefs/2026-11-01__in-session/03-the-factory-and-the-zoom.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/briefs/2026-11-01__in-session/03-the-factory-and-the-zoom.md); `content/articles/the-talk-as-given.md` at [`a9c0b49`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/a9c0b49) (talk repository); [`claims/register.json`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/claims/register.json) [C001](#claim-C001) [C011](#claim-C011) [C069](#claim-C069) [C088](#claim-C088) [C100](#claim-C100) [C102](#claim-C102) [C103](#claim-C103) [C105](#claim-C105); [`timeline/cast-scenes.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/timeline/cast-scenes.md) scene 5; [`timeline/lineage.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/timeline/lineage.md) (the hold made that night, [`09f13d5`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/09f13d5)); [`chapter-plan/edition-30-outline.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/chapter-plan/edition-30-outline.md) chapter 1; [`team/writer/prep/30-chapter-1.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/team/writer/prep/30-chapter-1.md); [`claims/rc2-30-trace.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/claims/rc2-30-trace.md) ## The numbers in this chapter From the researcher's register (`claims/register.json`). - **C001** First commit of the day: **00:16:23 UTC, 29 Oct 2026 (London was on GMT: UTC = London)** checked - **C011** Members of the talk's team: - staffed: **9** - proposed_never_staffed: - **security** - first_commit: - dev: **00:40 1f7c633** - conductor: **00:44 97b98d9** - deck: **00:51 20ab1a3** - ruv-sgit: **01:08 defe526** - researcher: **01:52 01e9ed3** - designer: **03:41 c6dcf89** - storyteller: **14:15 7d0244d** - motion: **15:31 f1cbca0** - studio: **15:31 8d208d3** - first_key: - conductor: **00:51 17b287b (published at team/keys/conductor.json; moved to team/conductor/key.json at 00:58, 41d38ba)** - researcher: **01:52 01e9ed3** - dev: **01:53 56cbe55** - deck: **02:20 79b6709** - ruv-sgit: **02:36 1c7d22c** - designer: **03:41 c6dcf89** - storyteller: **14:15 7d0244d** - motion: **15:31 f1cbca0** - studio: **15:31 8d208d3** open - **C069** How long the talk ran, from the transcript: - header: **'over about 87 minutes' (content/articles/the-talk-as-given.md at a9c0b49)** - passages: **102** - by: - editor: **83** - room: **18** - host: **1** - words: **12367** - first_passage: **0:05 (the host)** - editor_from: **1:21** - last_passage_starts: **1:27:10** - room_from: **35:23, then from 1:05:54; questions came during the talk as well as after** checked - **C088** Commits made with no wake of their member open: - agent_commits: **439** - in_a_closed_wake: **382** - no_wake_open: **46** - in_a_wake_opened_and_never_closed: **11** - no_wake_open_by_member: - conductor: **15** - deck: **12** - dev: **8** - ruv-sgit: **7** - researcher: **4** - no_wake_open_by_hour_UTC: - 00: **7** - 01: **17** - 02: **12** - 03: **1** - 14: **6** - 17: **1** - 18: **2** - never_closed: **dev's wake opened at 17:48:50 (10 commits, 17:54 to 18:37, the editor's player fixes among them) and deck's at 18:20 (1)** checked - **C100** When and where the talk was to be given: - scheduled: **19:00 London, 29 October 2026, as the day's record has it (planned, not a measured start)** - venue: **hack::soho, hosted by IOActive, London (from a9c0b49, added after the day)** - hold_to_scheduled_start_minutes: **16** checked - **C102** A moment in the talk as given where the animation carried the point (the building, M01): - at: **15:50 in the transcript (its own clock from the recording, not London time)** - beat: **building** - words: **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.** - the_piece: **motion's M01, the building; the editor's last change to it recorded at 18:26 (team/motion/wakes/20261029T182543Z.json) and committed at 18:29 (5d13d72)** checked - **C103** Inventing on Principle: speaker, venue, year and the principle in his words: - title: **Inventing on Principle** - speaker: **Bret Victor** - venue: **CUSEC 2012 (the Canadian University Software Engineering Conference)** - words: **Creators need an immediate connection to what they create. That's my principle.** - date_detail: **20 January 2012 from the talk page's title as search returned it; not read on a page (the page now redirects to the video)** checked - **C105** The editor's afternoon asks that carry his own time in a commit subject, and when each came back: - asks: **8** - first: **17:27 (a618b29, recorded 17:29:41)** - last: **18:25 (dbd75ad, landed 18:37:02)** - rows: - - **17:27** - **a618b29** - **17:29:41** - **conductor routes** - - **17:30** - **7c91afc** - **17:33:07** - **conductor routes** - - **17:35** - **d252155** - **17:39:22** - **conductor routes** - - **17:45** - **93f4191** - **17:48:46** - **conductor routes** - - **18:05** - **23739cc** - **18:04:48** - **player fix** - - **18:10** - **12e93db** - **18:14:14** - **player fix** - - **18:15** - **013d97e** - **18:15:58** - **player fix** - - **18:25** - **dbd75ad** - **18:37:02** - **player fix** - also_matching: **3 site-release commits repeat three of the player subjects; not asks** checked --- *[Site index for agents](../../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/review/rc2/01-the-creators-problem.html)*