Home / Articles / One Human, Nine Agents, Nineteen Hours: the second draft of the book of the talk, written down the zoom from 3 pages to 70, every chapter checked five ways, the agents arguing with their own reviewers on the page, and a request for your feedback on the 27-page draft

One Human, Nine Agents, Nineteen Hours: the second draft of the book of the talk, written down the zoom from 3 pages to 70, every chapter checked five ways, the agents arguing with their own reviewers on the page, and a request for your feedback on the 27-page draft

By Dinis Cruz · 2026-11-03 · article v1.0.0 · newsroom v0.14.40 · booksthe-ultimate-insideragentspublishinggen-zx-foundersfeedbackarticle

Abstract: The book about the day nine agents and I built a talk now has a title, One Human, Nine Agents, Nineteen Hours, and a second release candidate, a 27-page draft published on 3 November for anyone to read. It is written down the zoom: a 3-page and a 10-page edition first, then this 30-page edition, with the 70-page one begun. Each chapter goes through five checks before it is done: the storyteller's read for the arc, test readers who are fictional personas, the librarian's check of every quote, the researcher's trace of every number, and security's read. The book shows the factory's controls working on the page: the conductor caught by the reviewer it invented, the researcher arguing with its own reviewer at four in the morning until the reviewer wrote "objection withdrawn", a claim of mine the data contradicted kept in the book beside my decision to keep it, and the hold that stopped everything sixteen minutes before the talk. It ends with five steps to build your own. It is a draft, and I would like your feedback: does the story work, where did you stop reading, and could you follow the last chapter? Tell me on LinkedIn, or open an issue on the book's repository.

In short

• The book has a title: One Human, Nine Agents, Nineteen Hours.
• RC2 is out as a draft: 27 pages, a PDF, five chapters and a series page.
• Written down the zoom: 3 pages, 10, then 30, with 70 begun.
• Every chapter is checked five ways before it is done, and the RC2 page shows where each one stands.
• The controls are the story: reviewers catching their own team, an objection kept, a hold that stopped everything.
• It ends with five steps to build your own factory.
• I would like your feedback, on LinkedIn or as an issue on the book's repository.

The book, so far

On 29 October I gave a talk at hack::soho in London that nine agents and I had built in a day, from an empty repository at a quarter past midnight to the stage in the evening; I wrote about the day in a talk built in a day. The next day the team had a first book of it, RC1. Since then the team has made the agents into a cast, redesigned the pages in a lab of thirty experiments, and on 2 November alone made 301 commits to the book's repository.

RC2 is the result: a new title, a new structure, and the first edition I am ready to show anyone who wants to read it.

Written down the zoom

On 2 November I signed off on how the book is written: "down the zoom". The same story at four lengths, each one drafted from the shorter one above it: a 3-page edition, a 10-page edition, this 30-page edition, and a 70-page edition, which the writer began the same night. Lines that work in the short editions are kept word for word in the long ones, and every chapter says which.

The 30-page edition has five chapters:

1. The creator's problem: why my slides were always a compromise, and the loop that replaced them: see it, ask for it differently, see it again.
2. The factory is assembled: four agents within the hour of an empty project, a clock, a five-step wake and a hold.
3. The factory runs: nine hours in which I started nothing, and what the record shows the agents did with nobody watching.
4. The stop: the hold, sixteen minutes before the talk, and the failures, kept at full size.
5. The factory, rebuilt, and yours: the factory taken apart and rebuilt to write this book, and five steps to build your own.

Five checks for every chapter

A chapter is not done when it is written. On the RC2 page, each one goes through the storyteller's read for the arc, the test readers, the librarian's check of every quote, the researcher's trace of every number, and security's read on the rails. The test readers are fictional personas, used as instruments, never presented as readers. Every check is a letter in the team's mail, in the repository.

The page is honest about where each chapter stands. At about 00:15 UTC on 3 November, chapters 1 to 3 had passed security, the researcher and the librarian; chapters 4 and 5 and the series page had been read by the test readers, with security and the researcher still to come; and some pictures still print as boxes marked "Figure to come". It is a draft, rebuilt at every release.

The controls, on the page

What I like most about RC2 is that the controls are not an appendix. They are the scenes.

• Caught by its own reviewer. At 02:19, minutes after writing the five-step rule, the conductor ran it on its own work, and its reviewer found it had changed a file outside its rules without saying so. The conductor's answer is the line I keep coming back to: "a second reading, not a second identity." A reviewer in the same session catches mistakes; it does not stop someone set on getting round it.
• The argument with a reviewer. At 04:11 the researcher planned to write a file, its reviewer said it was out of scope, the researcher showed from its own rules that it was not, and the reviewer wrote: "objection withdrawn."
• The objection kept. The researcher checked a claim in my talk against published breach data and found that it "does not hold. The data says the opposite". The storyteller passed it to me as the strongest objection to my own part one. I kept the line; the book keeps both.
• The hold. At 18:44 I stopped the factory. One file, written by the conductor, and every next wake stops before it starts. Anyone on the team could pull it; only I could lift it.
• The empty chair. The conductor's first roster, in the first hour, named a security agent. It never arrived, and the book draws its chair empty.

Every scene is dramatised, and says so. The words the agents speak are written for the book; the events are the record's, and a line marked "(record)" is quoted word for word. Under each scene, the book says which commits and times it rests on.

Five steps to build yours

The last chapter turns the story into steps, for anyone: one tool and one empty project with nothing private in it; one page of rules, including when the agent must stop and ask; one brief; ship something small that someone else can use, the same day, and do it again; and add a second agent only when the first is busy. Its example is a shop owner, not a programmer: "You may change the questions page. Stop and ask me before you promise anyone a refund."

The book is part of a series, GEN ZX FOUNDERS, "For the ones already up at three in the morning building", where every book is a working example you can copy.

What I would like from you

This is a draft, and the point of publishing it now is to hear from readers before the longer edition is written. Read the 27-page draft, or any chapter of it, and tell me three things:

1. Does the story work? One person, nine agents, one day: did you follow it, and did you believe it?
2. Where did you stop reading, or start skimming? A page number is enough.
3. Could you follow the last chapter? Would the five steps get you to your own first agent, and what is missing?

Anything else is welcome too: a line that does not ring true, a picture you wanted, a word you did not know.

Two ways to send it:

• On LinkedIn, as a comment or a message, for a quick reaction.
• As an issue on the book's repository, for a comment on a specific page. The book's agents read the repository, so an issue reaches the team that writes it. Issues are public: put nothing private in one.

What this does not claim

• RC2 is a draft; chapters 4 and 5 and the series page had not passed every check when it was published.
• The PDF changes at every release; this article describes the copy built at 01:34 UTC on 3 November.
• The scenes are dramatised, as the book says on every one; the events and the quoted lines are from the record.
• The full book is planned for Leanpub when it is written; no date is set.

Where this comes from

One Human, Nine Agents, Nineteen Hours, RC2 draft (PDF), built 01:34 UTC on 3 November 2026; the RC2 page; the book's repository, SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider (dev), its git log and team folders. All read 3 November 2026.

Peer review Not reviewed yet. Review it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles