# The 10-page edition, page by page

> One Human, Nine Agents, Nineteen Hours, the 10-page edition, one page at a time, with what each rests on.

*Source: <https://the-ultimate-insider.book.sgit.ai/review/ed-10/pages.html> · site v0.1.514 · generated from the same content as the page, so the two cannot drift.*

---

the 10-page edition · page by page

# The 10-page edition, page by page

The draft one page at a time, as on a tablet, with what each page rests on beneath it.

Each page here is a printed page of this edition. 10 pages, from [editions.json](../../review/editions.json); the same chapters with their links are in [the edition online](index.md).

or the arrow keys

## The creator's problem · page 1

On stage: the editor, alone.

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 29 October I gave a talk where I mostly did not have to. When a thing had to move, I pressed play and it moved. When it was not quite saying what I meant, I asked for it differently and saw it again within the hour. I had a feedback loop on my own medium.

Narrator. What gave me that was not a better slide tool. It was a factory: a team of AI agents, gathered around one objective, run for a day, and taken apart when the job was done. This book is about the factory. The talk was what it happened to make that day.

Figure: the editor at a lectern with a play button; behind him, the factory's nine stations.

An agent , here, is an AI that works in a loop: it reads, decides, acts with tools, and checks the result.

The talk of 58 beats; that it was given that evening rests on its transcript, added to the record after the day.

**Rests on** C015 C069

## The factory is assembled · page 2

On stage: the editor; then dev, the conductor, deck, ruv-sgit (each card appears as it arrives).

Narrator. A quarter past midnight: an empty project. By twenty to one it held a brief and one page of rules, and the team had begun to arrive.

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.

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.

Conductor (pacing) : I keep the time. Everyone gets a slot, and anyone can pull the hold.

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

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

Narrator. The build, the check and the brief came from things I had built before. The hold was made that night. What was new was having them all at once, as a team: four within the hour, the rest through the day. That is how a factory gets cheap: yesterday's experiment is today's part.

Figure: the cast cards for the four, with when each came on stage and its commits, each figure with its id in small type.

If you want to start now, the last page has the five steps; the pages between are why they work.

Working as a team of several? Each person runs their own agents under their own page of rules; together you share one brief, one board where the work is written down, and one hold. Write down who may lift the hold when its owner is away; until you have, nobody does.

Dramatised. Rests on each agent's first commit after midnight.

**Rests on** 2e4b1f4 1f7c633 97b98d9 20ab1a3 defe526 C011 C014 C022 C071
Open: [`2e4b1f4`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/2e4b1f4) · [`1f7c633`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/1f7c633) · [`97b98d9`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/97b98d9) · [`20ab1a3`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/20ab1a3) · [`defe526`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/defe526)

## The machine, before dawn · page 3

On stage: as page 2, and the researcher (from about two).

Narrator. In the small hours, the conductor built the factory's machinery.

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.

Narrator. It ran the five steps on its own first piece of work, and its own reviewer found against it. (A reviewer is a second agent that reads the plan before the work and the result after it.)

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)

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.

Dramatised. Rests on the schedule, the five-step wake and its first review, between 01:39 and 02:19; the reviewer's and the conductor's lines are theirs, from that night's records.

**Rests on** 09f13d5 8c66751 5700bab c8f6f8f team/conductor/debriefs/2026-10-29__the-five-step-wake.md
Open: [`09f13d5`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/09f13d5) · [`8c66751`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/8c66751) · [`5700bab`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/5700bab) · [`c8f6f8f`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/c8f6f8f) · [`team/conductor/debriefs/2026-10-29__the-five-step-wake.md`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/blob/298be4e/team/conductor/debriefs/2026-10-29__the-five-step-wake.md)

## The factory runs on its own · page 4

On stage: six agents. The editor's chair is empty from five in the morning to two in the afternoon.

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

Narrator. Each agent could change only the files its page of rules named, and a reviewer checked every plan against that.

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

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

Narrator. ruv-sgit sent deck a picture for the talk. Deck sent it back.

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

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

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

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.

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.

Dramatised. Rests on the wakes started by the schedule alone from 05:00 to 14:00, and on the researcher's dispute and its reviewer's "objection withdrawn" (04:11), deck's review (06:21), the designer's note (10:49) and the conductor's note (10:05).

**Rests on** C087 af0010b 78b89b9 56c680b 09317d9
Open: [`af0010b`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/af0010b) · [`78b89b9`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/78b89b9) · [`56c680b`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/56c680b) · [`09317d9`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/09317d9)

## The loop, with the creator in it · page 5

On stage: all nine: the storyteller, then motion and studio, join in the afternoon.

Narrator. When I came back, the loop began: I looked, I asked, they changed it, I looked again. The player, the thing that let me press play, was my first priority, and it landed in the afternoon. I was still asking for fixes to it in the last hour before the talk.

Narrator. My story leaned on a claim that the outside of an organisation is more mature than its inside. 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.

Narrator. It came to me. I kept the line in the talk, my own call, and the researcher's objection went on the record beside it. The book keeps both.

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 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.

Dramatised. Rests on the player as the main priority (about 13:50) and its port (15:07); the last fixes inside a wake left open (C088); the R5 argument (14:33, 15:02); studio's refusal (17:47, made by the session's own check).

**Rests on** c9ced4e 3314ffe dbd75ad 2726f0e b208a16 bd3cdad C088
Open: [`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) · [`2726f0e`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/2726f0e) · [`b208a16`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/b208a16) · [`bd3cdad`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/bd3cdad)

## The stop at 18:44 · page 6

On stage: all nine. Security's chair, planned at midnight, is empty.

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) The conductor wrote one file, and every new piece of work stopped. What was already in flight still landed. The hold had been there all day. I asked for it once.

Figure: ruv-sgit's strip, the conductor after the hold, talking to security's empty chair.

Narrator. Anyone on the team could stop everything. Only I could start it again. That is why I could let them run through the night.

Narrator. Why stop then? I have given three answers, and the book keeps all three. On the day: my usage was at 95%. In the early hours of 31 October: the 95% was a footnote; the real reason was that we had no tested way to take in changes during the talk. That evening: the 95% was the token usage.

Dramatised. Rests on the hold at 18:44, my own words in the hold file, and what landed after it; the talk due at 19:00; my later two accounts of why, given after the day.

**Rests on** 867f8c2 2ed6427 88b8f00 C006 C024 C065 C089 C100
Open: [`867f8c2`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/867f8c2) · [`2ed6427`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/2ed6427) · [`88b8f00`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/88b8f00)

## What did not work (the interview) · page 7

On stage: all nine.

Figure: ruv-sgit's strip, the researcher interviewing deck about the claims that did not hold.

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

Narrator. The talk was planned in parts.

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

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

Narrator. 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. When the freeze lifted, nobody carried the correction back in, and the out-of-date figure reached a slide in the talk. The checks found it; the freeze hid it. 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 needed more rounds than one day gave it. The checks worked, and they also missed. Saying where is part of the method.

Dramatised. Rests on the talk's register and on each member's own debrief.

**Rests on** C027 C029 C030 C031

## The factory, taken apart and rebuilt · page 8

On stage: the nine fade; a new bar begins.

Narrator. That night the factory was taken apart. The next day I built a second one from its parts, rule for rule, to write the book you are reading: a conductor, a librarian, a historian, a researcher, a storyteller, a publisher and more, each with its own page of rules. Its first job was to read the first factory's record.

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.

Dramatised (the conductor's line). The book's own team, ported on 30 October; the Web Summit team as I described it on 1 November. The second and third factories are this book's record, not the talk's.

**Rests on** briefs/2026-10-30/1-book-conductor-brief.md briefs/2026-11-01__in-session/03-the-factory-and-the-zoom.md
Open: [`briefs/2026-10-30/1-book-conductor-brief.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/briefs/2026-10-30/1-book-conductor-brief.md) · [`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)

## Your factory, starting tomorrow · page 9

On stage: your own, empty for now.

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.

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."

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."

Your agent builds, you check: ship something small that somebody else can use, the same day. Then do it again.

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.

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.

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

Want the whole story? The longer edition gives each of these beats its own chapter, with its maps and a "do this now" for each.

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.

**Rests on** C101 C037

## A book about you doing it · page 10

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.

The series' name, line and idea, from its own site; G1, signed 31 October.

The talk team's record of 29 October, its history read commit by commit, and the talk's transcript, added after the day; the book team's timeline of who was on stage when, and its quotes from the record; the cast guide; the book's register of claims, for every figure; the readers' reports on the drafts.

The exact files and commits behind each of these are in the book's index, under the editions.

**Rests on** gen-z-developers.sgit.ai (read 31 October 2026)

or the arrow keys

---

*[Site index for agents](../../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/review/ed-10/pages.html)*