# The ultimate insider, the book: one day, ten agents, one talk

> The book of The ultimate insider talk: how one person and a ten-agent team built a talk in nineteen hours on 29 October 2026, with the record to prove it, and the controls that kept the team in check. First edition on Leanpub on Monday 2 November 2026.

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

---

The book of the talk · first edition on Leanpub, Monday 2 November 2026

# The ultimate *insider*, the book

One person, ten agents, one day: how a talk got built, and how the team that built it was kept in check.

- **Edited by Dinis Cruz**
- Written in public, from the record
- Working title: the editor signs the title in round 1

[The plan](plan/index.md) [The manuscript](book/index.md) [The brief](brief/index.md)

29 October 2026, from the brief

19

hours from the first commit at 00:16 to the talk at 19:00

18:46

the last change, release v0.1.209, two minutes after the hold at 18:44; nothing changed after it

814

commits by then: 603 by Claude, 210 release commits by GitHub Actions, 1 by the editor

23:19

the editor's merge to main published the finished work as v0.2.0, with no change to it

The conductor's counts from the talk's git log at `298be4e`, [corrected from the brief](admin/docs/corrections.md); the researcher re-checks every number before it goes in the book.

## Two threads, told as one story

-

### The workflow

How the team was set up, briefed, scheduled, keyed, reviewed, held and released, and how to replicate it elsewhere. The main thread.

-

### The argument

The talk itself: agents are the insider that has none of the old attacker's limits, and brakes are what let us go faster.

-

### The two as one

The team that built the talk is itself the ultimate insider, held in check by its own policies. The book shows the controls working on itself.

## The gap it fills

The public conversation says agents cannot be made to work, are too risky, and do not pay back. Here is a counter-example with a timestamped record, and the controls that made it safe: the 18:44 hold when the editor's usage reached 95%, signed session keys, the pinned key tool, a review before and after every wake, and decisions that only the editor can sign.

It is not a dump of the record. It is analysis written with hindsight: what was achieved, in what order, why it worked, what it cost, what went wrong, and what it means. The failures stay in.

## The dates

-

Monday 2 November 2026

### On sale on Leanpub

The first edition, PDF and EPUB.

-

Monday 9 November 2026

### Web Summit

On Amazon too, and a paperback proof ordered.

[The whole plan, round by round](plan/index.md) · [What the editor still decides](decisions/index.md) · [Who writes it](team/index.md)

---

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