# Decisions > What the editor decides by signing: 11 open, 11 decided. *Source: · site v0.1.26 · generated from the same content as the page, so the two cannot drift.* --- ## Q3 (open): The title The editor, 30 October: an agent looks at it first. The market stream (synthetic readers and positioning) tests the candidates on [the book page](../book/index.html#title) and better ones against the readers, and proposes; the editor signs in round 1. ## Q4 (open): The editor's voice memos and the claude.ai transcripts of 29 October Not in the talk's repository; the editor holds them: his voice memos of 29 October (the morning's narrative memo, the 13:50 feedback round, the 15:00 decisions round), the claude.ai session transcripts in which the briefs were written, and any recording of the talk on stage at 19:00. Do any of them go into the book's source? ## P0 (open): Sign the chapter plan The storyteller's draft 2 in `chapter-plan/` (not signed): thirteen chapters with word budgets, every number by register id, the evidence by index, timeline and control. Nothing is written until it is signed. O1 to O5 below are its open questions; signing the plan answers them as drafted unless you say otherwise. Asked by the storyteller. ## O1 (open): The length From `chapter-plan/open-questions.md`. The storyteller proposes A for Leanpub, with B as the fallback if round 2 runs short. - A: about 48,000 words, thirteen chapters (the plan as drafted) - B: about 32,000 words, ten chapters (4 and 6 folded in, 9 to 11 shortened) ## O2 (open): The opening The storyteller proposes A: the hold is the thesis in one scene. - A: open on the 18:44 hold, then go back to midnight (the plan as drafted) - B: open at midnight and tell the day in order, the hold in chapter 8 ## O3 (open): The talk as given May chapter 10 quote the cleaned transcript and your debrief, added to the talk's repository after the day (`a9c0b49`), and show what you said on stage beside what was planned? If not, chapter 10 becomes a short section of chapter 8. ## O4 (open): Your voice in the book Your voice memos and claude.ai transcripts of 29 October are not in the record (the same ground as Q4). - A: an interview with you feeds chapters 6 and 12 - B: the book uses only what is in the record ## O5 (open): The braid Each workflow chapter carries the beat of the talk its control answers (the plan as drafted), rather than the argument in chapters of its own. Sign or strike. ## C011 (open): "A ten-agent team" The brief says ten; the researcher's register counts nine staffed agents, with security proposed and never staffed (claim C011). Which wording does the book use? Chapters 0 and 6 wait on it. Asked by the researcher. ## L1 (open): The price on Leanpub, with a floor From `publishing/LEANPUB.md`. The publisher recommends B: "a floor" was your word in the brief, and a minimum can be lowered later more easily than raised. - A: free minimum, $15 suggested - B: $9.99 minimum, $19.99 suggested - C: $4.99 minimum, $14.99 suggested ## L2 (open): Which branch Leanpub builds from The repository's default branch is `dev`; name it explicitly when you create the book. The publisher recommends `main` for both, so Leanpub builds only what you merged. - main for previews and publishing - dev for previews, main for publishing ## Q2 (decided): The hours, and the editor's usage The editor, 30 October about 02:20 UTC: "every agent will continue to fire every hourly", and on usage: "we still are only at 26% usage. So we're good ... if you max out, just, you know, you just wait until the 5 hours go around." Round the clock, hourly; a member that hits the limit waits for the reset rather than holding the team. Each member finishes when its Done when list holds (WAKE.md, Finishing). ## Q1 (decided): The repositories and their sites Signed by the editor, 30 October: SGit-AI__Website__Book__The-Ultimate-Insider at the-ultimate-insider.book.sgit.ai (this one, informed), and SGit-AI__Website__Cold-Read__The-Ultimate-Insider at the-ultimate-insider.cold-read.sgit.ai (the blind one). ## Q5 (decided): The licence of the text Signed by the editor, 30 October: CC BY 4.0 for the text, as for the Gen ZX book. Code Apache-2.0. ## S1 (decided): The centre of gravity The third of three candidates: not the argument alone, not the method alone, but the two as one story. The team that built the talk is itself the ultimate insider, and the book shows the controls working on itself. ## S2 (decided): Analysis with hindsight, not raw content The record is quoted as evidence; the writing explains it. A chapter that is mostly quoted record is sent back. Every chapter ends with where it came from. ## S3 (decided): The dates Leanpub on Monday 2 November 2026; Amazon and a paperback proof by Web Summit, Monday 9 November. ## S4 (decided): Two repositories and the one-way valve The informed book repository and the blind repository run in parallel, from the talk's repository pinned at `298be4e`, read-only. Nothing flows from here to the blind one. ## S5 (decided): The market-research and positioning stream starts at once Synthetic readers, three positioning statements tested against them, the comparison set, and the Web Summit plan, in parallel with the writing. ## S6 (decided): The span of the day the book covers Signed by the editor, 30 October: from the first commit (00:16) to the last commit before 19:00, the talk. In the record that is the last work commit at 18:45 and release v0.1.209 at 18:46; the merge to main at 23:19 only published the work as v0.2.0. ## S7 (decided): Which version of the talk's repository each team reads The editor, 30 October: the Cold-Read team stays pinned to `298be4e` (the same content as `cb5b996`, v0.1.209, the last release before 19:00; only `./version` differs). The book's team reads the talk's repository as it keeps growing, because the editor adds material there after the day (the transcript of the talk, interviews with each agent): the two repositories work in sync. The record of the day stays the history up to `298be4e`; anything later is cited by commit as added after the day. ## S8 (decided): Every team runs on the talk team's machinery The editor, 30 October: the admin section, the workflow of the agents, the way they are recorded, the change control and the guidance for agents are the same on every team as on the team that built the talk; nothing is reinvented. Ported here from `298be4e` (see [admin](../admin/index.html)); the Cold-Read team is asked to do the same in its hand-off. --- *[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/decisions/index.html)*