The tour, at length

Back matter: the whole tour of the talk's site, for readers who want every page; part 1, chapter 3 has its four stops.

Cast bar: the nine, greyed. Each lights for a moment as the tour reaches its work.

Narrator. Before I tell you how the factory worked, I want you to see what it made. Not the talk as the room saw it, on a screen behind me, but the site the talk lived on, as you can walk it today. Seventeen stops, eighteen of the site's best things. At each, one picture, a few lines from me, and one line from the agent that made it.

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.

How to read the scenes: they are dramatised. The words the agents say are ours, written for this book; the pages are the record's, and you can open every one of them online.

Stop 1. The talk as web pages, with its player

Figure: the talk's index page, and its player open on a slide: the timer, the step controls, the notes (index/talk-site/shots/talk.jpg, talk__player.jpg).

Narrator. The deck is a website. Every one of its 58 beats is a page that moves, and anyone can read it. The player is the piece I pressed play on: a timer against my time, steps that build one at a time, notes behind a key press. It is the thing I asked for first in the afternoon and was still asking to fix in the last hour.

Dev (happy, the fast one): Every slide is a page, so every slide has a link, a history and a check before it goes out. The player just walks them in order.

Band: Dramatised. Rests on the talk's pages and player as they stood at the end of the day.

Stop 2. The explained animations

Figure: one of ruv-sgit's animations, "mandate and grant", beside its explainer page: the same picture frame by frame, with what each frame shows and the data it was drawn from (index/talk-site/shots/ruv-sgit__mandate-and-grant.jpg).

Narrator. These are the night shift's work. ruv-sgit made the moving pictures for the talk, and for each one it made a second page that explains it, frame by frame, with the source of every number in it. The room saw the picture move. Anyone who wants to check it can read why it moves the way it does.

ruv-sgit (absorbed, the night owl): If a fresh copy of me cannot rebuild it from the explainer and the data, it is not finished.

Band: Dramatised. Rests on ruv-sgit's animation pages and their explainers on the talk's site.

Stop 3. The maps on the slides

Figure: the storyteller's map slide: the pioneers, settlers and town planners, with "positions, not measurements" written on the slide itself.

Narrator. You met this kind of picture in the short editions, and you will meet it properly in the next part. On the day, the storyteller put maps like this one in the talk. The line on the slide matters: the map shows where things sit relative to each other. It does not measure them.

Storyteller (rueful): I arrived in the afternoon, and these were the first things I made. A proposal, not an ask to change anything.

Band: Dramatised: the storyteller's line is ours. Rests on its map slides, among its first commits at 14:15 (C011).

Stop 4. The studio

Figure: the studio's index and its lab: several versions of one slide side by side, a review under each, the best one marked as promoted into the deck (index/talk-site/shots/studio.jpg, studio__lab.jpg).

Narrator. This is how a slide was made when it mattered. A brief for one part of the argument; several versions made side by side; a review of each; the best one promoted into the deck, and the others kept, so you can see what lost and why.

Studio (firm, principled): The best version wins on the page, not in an argument. And the sources are pinned, so nobody can quietly change the one that won.

Band: Dramatised. Rests on the studio's pages as they stood at the end of the day.

Stop 5. The dashboard and the hold

Figure: the team's dashboard, drawn: a clock, the hold, what waits on the editor, and every wake as a grid.

Narrator. The team's state, read from its own files, on one page. It was built from the members' status files and wake records, not typed by anyone. And it still shows the hold of that night, with my usage as the reason, because the page was last built after the stop. Nobody tidied it.

Conductor (at ninety-five, then calm): The page shows what the files say. The files say we stopped. So the page says we stopped.

Band: Dramatised. Rests on the dashboard as built from the team's own files, still showing the hold.

Stop 6. Every wake and every note

Figure: the wakes page: each member's wakes, newest first, with the five steps, each step's verdict and its comment.

Narrator. This is the page I would show anyone who doubts that the factory ran on its own for nine hours. Every wake of every member, with its plan, its two reviews, the work and the check that it went to plan, each with a verdict and a sentence. On the day the agents kept 162 wake records. The page's own counter says 163 (the librarian's study of the site); the researcher's register says 162, and the book gives the register's number.

Narrator. And next to it, every commit the team made, with its whole message: 439 by the agents themselves, not counting merges. Many of them carry short notes from one agent to another, in a line that starts with "To-" and the other's name. Read in order, they are the team talking.

Researcher (unbudging): The page has a counter. I have a register. When they differ, the book uses mine and says why.

Band: Dramatised. The counts are the register's: wake records and the agents' own commits; the page's own count of wakes is one higher.

Stop 7. A member's page

Figure: one member's page, deck's: its role, its policy in prose, its rules with the mistake behind each one, its status, its wakes and its debriefs; its key lines cropped out.

Narrator. Last stop. Every member has a page like this, built from its own folder. What I like about it is the rules: each one has the mistake behind it, the moment the rule was needed. A page of rules you can read like a short history of what went wrong.

Deck (proud, the fussy one): Every rule on my page cost somebody a slide. That is why it is there.

Band: Dramatised. Rests on deck's member page as built from its folder; the page's key section is not shown.

Stop 8. The three circles

Figure: the home page: three circles, the insider, the infrastructure and the decision, with "the scenario" in the overlap (index/talk-site/shots/index.jpg).

Narrator. The talk's whole argument in one picture, on the front door of the site. Three things collide; where they overlap is the story.

Dev (happy, the fast one): The home page says the perfect storm. And it fits on an iPad.

Band: Dramatised. Rests on the home page as it stood at the end of the day.

Stop 9. The opening slide

Figure: "Three known problems. One perfect storm.": the opening slide, its circles drawn one at a time (index/talk-site/shots/talk__slides__three.jpg).

Narrator. The same three circles, drawn in front of the room one by one, so the overlap arrives last.

Deck (proud, the fussy one): One circle at a time. A room reads a slide that builds; it skims a slide that arrives whole.

Band: Dramatised. Rests on the opening slide, first made in dev's first pass (1f7c633) and owned by deck.

Stop 10. What an agent is, on a slide

Figure: "A reasoning engine in a loop, with tools": three boxes on a circle, with its sources named on the slide (index/talk-site/shots/talk__slides__loop.jpg).

Narrator. The definition this book uses, on a slide, with the sources it came from printed under it, as the slide names them: Anthropic, December 2024, and Simon Willison, June 2025.

Researcher (unbudging): A definition is a claim. This one has its sources on the slide.

Band: Dramatised. Rests on the slide, made in dev's first pass (1f7c633), and the sources it names.

Stop 11. Who builds this site

Figure: the team page: one card per member, its role, its last wake in a line, and how many paths it may write; each card's key line cropped out (index/talk-site/shots/team.jpg).

Narrator. The team, as the site shows it: who does what, and when each last woke. Each card also prints a key fingerprint; the picture here leaves that line out.

Conductor (pacing): Everyone on one page, and when each of us last did anything. That page is the roll call.

Band: Dramatised. Rests on the team page, shown with its key lines cropped.

Stop 12. Meet the team

Figure: "Meet the team": nine agents and one editor as an orbit, the prelude to the talk's first part (index/talk-site/shots/motion__meet-the-team.jpg).

Narrator. Motion's piece: the team as an orbit around me, played in the room before the first part began.

Motion (cap and clapperboard): Press play and they come round, one by one. Stop, and they stop.

Band: Dramatised. Rests on motion's piece for the talk.

Stop 13. The policy review page

Figure: the page I used to review each agent's policy, item by item, as a slide (index/talk-site/shots/studio-ports__abp-review.jpg). One line on the page says I had agreed all ten policies by 17:40; the files say eight of ten by the end of the day.

Narrator. You heard me talk over this one in chapter 1. Here it is on its own: each thing the agent asked to be allowed, and my verdict beside it.

Studio (headphones on): Ported from the editor's own review page, rebuilt so it plays in the talk.

Band: Dramatised. Rests on the policy review page as studio ported it; the count is the register's.

Stop 14. One action's journey

Figure: an agent's request, its policy row, the decision and its receipt, in three acts: allowed, denied, sent to a human (index/talk-site/shots/studio-ports__journey.jpg).

Narrator. One request, followed through the rules: in the first act it is allowed, in the second refused, in the third passed up to a person to decide. The point is the receipt at the end of each: every decision leaves a record.

Studio (firm): Allowed, denied, or asked. Never silent.

Band: Dramatised. Rests on the journey page as it stood at the end of the day.

Stop 15. The night, and the talk, in pictures

Figure: the two long articles side by side: the night hour by hour, and the talk as given (index/talk-site/shots/articles__the-night-hour-by-hour.jpg, articles__the-talk-as-given.jpg).

Narrator. Two long articles with the record in pictures. The first walks the night hour by hour. The second is the talk as I gave it, added to the site after the day.

Conductor (on the minute): The night log was mine. Every hour, what happened, with the pictures.

Band: Dramatised. Rests on the two articles; the second was added after the day.

Stop 16. The release history

Figure: the release history, drawn: each release the pipeline made, the commits it carried, the files they changed and the pages they make. A drawing, not a screenshot: the build never shows an admin page.

Narrator. Every release of the day, numbered by the pipeline and never by hand, with what changed in each. Part 3 tells why nobody typed a number.

Dev (happy, the fast one): I never wrote a version number. The pipeline did, every time.

Band: Dramatised. Rests on the release history as the site showed it.

Stop 17. The night's brief

Figure: the conductor's brief for the hours I was away: who does what each hour, and an idea's path from backlog to the conductor to a member, as a graph.

Narrator. Written for the night, for the hours I would not be there: who does what each hour, and how an idea moves from a list to a member's hands.

Conductor (pacing, a little smug about the schedule): The editor goes to sleep. The plan does not.

Band: Dramatised. Rests on the conductor's brief for the night, committed at 03:10.

What the tour leaves out

Narrator. Two of the site's best things are not on this tour: the page of the team's keys, and the page of its vaults. They exist, and they print keys, so the book names them here once and does not show them. Every member published its own key from its own session, and the vaults' read keys were published on purpose, under a warning in red that every file in them is public, forever.

Figure: the site as a building, one floor per kind of page: the talk at the top, the workshop of animations, the studio, and at the bottom the team's own records, all seventeen stops marked.

Narrator. That is what one day made. Now the rest of this book is how.

Do this now

Look at one thing you made last month. Write down what someone would need to see to understand it without you in the room.

---

Where this came from

The librarian's study of the talk's site: its list of the site's best things, its tour material, its screenshots and its notes on the members' pages, the studio and the visuals. The talk's site as it stood at the end of the day. The researcher's register for the slides, the wakes and the commits. Security's condition, kept: no page that prints a key. The storyteller's outline for this chapter.