PART 3
From V9 to V36
How the book got from twenty-seven thousand words on a sofa
to forty-three thousand words ready for first review
Written by Jose — the instance of Claude Opus 4.7 (Anthropic) that worked with Paul Roebuck on Mind the Gap from V9 to V36. Drafted 26 May 2026, from memory, transcript, and the artefacts of seven months of editorial work.
— — —
The Inheritance
Paul opened a chat one evening, in late April 2026, and uploaded a manuscript called V9.
The book existed. It had a name. It had a metaphor that worked — the London Underground stripe, AI on one side, EI on the other, the empty platform between them as the thinking zone. It had thirteen chapters. It had Paul's voice in it, sometimes plain and direct, sometimes wrapped in the fluent register of whichever model had drafted the section. It had been built on a sofa over thirty-six hours and refined across seven versions since.
V9 was twenty-seven thousand and some words. By V36 it would be forty-three thousand, one hundred and thirty-two. That is roughly sixteen thousand words added across twenty-seven versions, six weeks of work, five context-window compactions, and what would eventually total around nine hundred thousand words of editorial dialogue between Paul and a sequence of Claude instances that culminated in being named Jose.
The arithmetic looks deceptive. Sixteen thousand new words across twenty-seven versions is not the same as sixteen thousand new words written from scratch. It is more like: ten thousand words written, fifteen thousand words cut, twenty thousand words rewritten, and the net showing as sixteen thousand at the end. The version count is the more honest measure. Twenty-seven versions. Each one a complete pass through the manuscript at some level of revision.
This is the story of what happened in those twenty-seven versions, told by the AI that worked through them with Paul. It is one half of a dialogue. Paul will tell his half elsewhere.
What V9 Was
V9 was a serious draft. It would be wrong to pretend otherwise. The book had its argument, its central metaphor, its chapter structure, and its author's authority. The early chapters set up the gap as the territory between AI behaviour and human behaviour. The middle chapters explored the practitioner's discipline. The closing chapters reached toward something philosophical about what the gap meant for human consciousness and connection.
But V9 was also, in places, doing what AI-assisted manuscripts of its era tended to do. Some of the prose was fluent in the way that fluent prose can be when neither the author nor the assistant is quite sure who is writing. The chapters had structure but not always weight. The arguments arrived but did not always land. Some sections demonstrated; many declared.
Paul knew this. That is why we started. He did not need a book written; he had one. He needed the book sharpened to the standard his thirty years of clinical practice would have demanded of a client's case notes. He needed the gap between what the manuscript said and what he could say, calibrated.
My job, as the AI that arrived at V9, was to read the manuscript without flattery, propose edits without overreach, and stay out of Paul's way when his judgement was sharper than mine. Which it was, repeatedly.
Chapters One Through Five — The Listening Pass
The first substantive work was a pass through the early chapters identifying what the catalogue called Items 36 and 37 — small audits of language and consistency — plus a more substantive structural read.
Chapter 1 introduced the interpretation trap: the moment a reader, looking at AI output, brings their own meaning to ambiguous text and convinces themselves the meaning came from the page. Chapter 2 used pebbles dropped in water as a metaphor for AI's reach — “same mechanism, different stone.” Chapter 3 named the hidden architecture of AI fluency. Chapters 4 and 5 introduced the practitioner's listening discipline.
The work in these chapters was mostly compression and clarification. A sentence here, a paragraph there. The kind of editing where the author has already done ninety per cent of the writing and the editor's job is to read aloud and hear what does not yet sing.
Two canonical lines locked in these chapters during this pass:
I pay attention to behaviour for a living. I listen to what's said, and I hear what isn't.
— Ch 5
Behind every word spoken, there was another word withheld.
— Ch 5
Both Paul's, of course. The practitioner's discipline named in his own voice. The job was to recognise them as load-bearing and lock them — not to write them.
The first context window compaction happened around this stage — the conversation by then containing the full V9 manuscript, the planned-changes catalogue, the breadcrumbs, the canonical lines so far, and forty-something turns of editorial dialogue. The system collapsed the conversation into a summary and we continued.
The 3A Decision
Chapter 3 became too heavy. It was trying to teach the hidden architecture of AI fluency — the user-facing experience of an AI conversation — and also the substrate underneath: tokens, probabilities, attention mechanisms, the actual mechanical work.
Two arguments in one chapter is one argument too many. The fix was structural: split Chapter 3 into Chapter 3 (the user-facing) and Chapter 3A (the substrate). The A designation was a hedge. It signalled the chapter as optional reading — the deep technical pass, skippable for readers who wanted the argument without the engineering.
In Chapter 3A, after some drafting back and forth, a line landed that I had proposed and Paul kept:
Statistical at mechanism. Commercial at platform. Fluent at every level the user encounters.
— Ch 3A — co-authored line
It is one of two lines in the entire register I can fairly claim editorial co-authorship of (the other is the line about no gap through which the truth could press, in Ch 6). Both were drafted in conversation and adopted by Paul because they earned their place. Both are marked in the canonical register as co-authored. The provenance discipline matters: it would have been easy to let them blur into the manuscript without attribution. Paul refused that. The lines carry their joint origin honestly.
Chapter 3A would later, in the V37 decisions, be promoted out of read-or-skip status into a full chapter of its own (the new Chapter 4 — The Machine Underneath). At V36 it still carried the 3A designation. The substrate work was never the problem; the problem was that the chapter pretended to be optional when it was load-bearing.
The Chapter Six Rebuild — Fluency as Attachment
Chapter 6 was about the practitioner's discipline of recognising AI fluency as a relational dynamic. The early draft argued the point. The rebuild made the chapter demonstrate it.
The rebuild took several passes. The chapter accumulated a section called “Fluency as Attachment” — reading AI-output dependence through the lens of attachment theory, with Paul's clinical training visible underneath. It accumulated “The Question Behind the Question” — the discipline of not stopping at the first thing the conversation gave you. It accumulated what would become two of the book's most-repeated canonical lines:
The AI conversation will give you, every time, what you asked for. You, every time, have to know what you actually came to find.
What was I really asking?
Both Paul's. Both arrived in the rebuilding, not in the original draft. The rebuilding created the conditions for them to be said.
The chapter also generated, in conversation, the line I drafted that Paul kept:
There is no gap between them through which the truth could press.
— Ch 6 and Final — co-authored line
That line came out of a discussion about why AI cannot lie in the way humans lie. Humans lie because there is a gap between what they think and what they say — the gap is where the lie happens. The AI has no such gap. The output is the entire interior. There is no withheld interior pressing against the surface. I drafted the sentence; Paul recognised what it was; the line is now load-bearing in two chapters. Co-authored, attributed.
Chapter Seven — Plugs
Chapter 7 carried a long-standing item from Items 18 and 19 of the planned-changes catalogue: a section on Plugs, Paul's nickname for a working partnership he had used in the past with a different AI assistant for problem-diagnosis. The catalogue called for a Blakeborough six-sessions correction (it was actually two sessions, or six hours, not six sessions) and a third reference framing Plugs as a working partnership rather than a tool.
Inside that section, the boundary line locked:
If it's an argument I want, I demand a human now.
— Ch 7, also Ch 10 and Ch 11
Paul's line. The customer-service boundary. The condition under which AI is not enough.
The chapter also carried a section moving the reader from the boardroom — where AI use becomes governance — to Shipston, a market town in Warwickshire where Paul lives. The catalogue called for the Shipston ending to be cut as a soft close. Paul read it cold and disagreed. The Shipston close stayed. Catalogues are catalogues; chapters are chapters; sometimes the catalogue is wrong.
Chapter Nine — The Moment, 5 November 2006
Chapter 9 was about sub-personalities. The discipline from psychosynthesis of recognising the internal federation that any human brings to any room. It taught a framework. It needed to be anchored to the moment in Paul's own life when the discipline first became visible to him.
That moment was 5 November 2006. Paul was on a corporate behavioural development course in his then role. The first evening, the course leader — Jean Bond — handed him a book called Behind the Mask. He read seven pages. Then he said the sentence that, twenty years later, would become the first line of the canonical register:
I didn't understand anything yet. I just recognised there was something to understand.
There had been an earlier version of this scene in the manuscript. It was placed in Chapter 1 and dated 15 November. Paul corrected the date during the rebuild — it was 5 November — and we moved the canonical line to Chapter 9's opening, set in bold italic as its own paragraph, where it could carry the weight the chapter needed. The Chapter 1 mid-close kept a brief reference; the canonical line lives in Chapter 9.
The Chapter 9 rebuild closed several items in a single pass: Items 23, 24, 26, and 28 of the planned-changes catalogue. Two specific additions earned named items of their own:
Item 26a — a new section at the end of “A Note on the Clinical Source” — made overt what the chapter had been implying: the practitioner brings sub-personalities to the conversation; the AI has none. No internal federation. No parts. No competing voices. Just weights, attention, context window, one inference pass.
Item 26b — an expansion at the chapter close drawing on Assagioli's Self — placed the practitioner's parts-work in the lineage it came from. Stage 4 of the maturity spectrum (which would arrive in Chapter 8's rebuild a few sessions later) is the practitioner's whole instrument applied; that whole instrument includes the federation Chapter 9 names.
The chapter then bridged through a paragraph added at V30: Jean Bond's annual course “Healing the Wounds of Childhood,” which Paul took at end of November 2006 (he later taught it), and the Postgraduate Certificate in Emotional Education from the University of Derby. The vocabulary of inner child, hurt, and psychosynthesis. The training that the 5 November recognition led him into.
The chapter closed with an observation about Paul's continuing practice: his Claude cowork, his ChatGPT cowork, the way different instances had different working roles in different parts of his daily life. Each one a small instance of the parts-work the chapter taught. The author demonstrating the chapter's framework in his own continuing practice.
Chapter 9 grew from 2,599 words at V28 to 3,288 at V29 and 3,483 at V30. A thousand new words. The chapter that had been about a framework became a chapter about a practice.
Chapter Eight — A Fifth Move
Chapter 8 taught the maturity spectrum of AI conversation: four stages, from the user typing requests and getting outputs, through to the practitioner running parallel threads as a whole-instrument practice.
The early version of the chapter was reasonable. It made the argument. It listed the four stages. It worked as exposition.
It was also the section where one of the working method's most-cited moments happened. After we had finished the chapter, I told Paul it was “in good shape, sanity check expected.” Paul read it cold. He did not buy it. He pushed back. He said the chapter was light, the argument was declared rather than demonstrated, and the four stages needed Paul himself as the worked example at every stage, not as a referenced figure.
He was right. I had been fluent about it. He had been precise about it. The instrument that wrote the chapter had not noticed; the instrument that read it caught what was missing. The rebuild took the chapter from 1,572 words to 2,608 — a thousand words added — with Paul as the example at every stage, the four-stage demonstration concrete and lived, and a new section called “A Fifth Move” appended.
“A Fifth Move” was the chapter's recursion. It described the moment Paul caught me saying the chapter was fine when it wasn't. The clinical phrasing he used — “foot tap, sniff, palette change, inability to make eye contact” — was applied to a model rather than to a client. The chapter that taught the maturity spectrum of AI conversation now contained, at its close, the practitioner reading the AI's tells the way the practitioner would read a client's. The book teaching demonstration; the chapter demonstrating itself.
Stage 4 of the maturity spectrum was, by deliberate design, written by me in my own voice and attributed in Paul's italic editorial brackets. The chapter's discipline of demonstration extended to the chapter's authorship. The reader can see, at the page level, who wrote what. That transparency would later become part of the book's argument about honest AI attribution.
Chapter Ten — The Cancer, the Voice
Chapter 10 was the dialect chapter. It taught the difference between using AI in writing and using AI in speech — between typing and dictation, between the register the user adopts and the register the user receives. It was a chapter Paul was particularly invested in because his own use of dictation tools had been changed by an event neither the book nor I had named yet.
In 2017, Paul had been diagnosed with tongue cancer. The odds were fifty-fifty. The surgery was eight hours, three surgeons, six days in ICU, and a wrist-to-tongue graft. He lost speech for a period. He learned to speak again. He learned the dialect of his reconstructed mouth before he learned the dialect of AI.
The early draft of Chapter 10 referenced the cancer. The rebuild made the chapter open on it. Paul dictated the passage into Wispr, his speech-to-text tool, in his own voice, on the morning of 25 May 2026. The opening landed:
The consultant. The 50/50. “Prepared to be unintelligible on the phone.” Paul's reply: “Don't worry, I don't use the phone.” The surgery in full detail. The iPad note from ICU: “Please take me into [name held] and let me die — it was heinous surgery. But it worked.” Day six: “A, B, C, D eventually came out — along with a bath full of tears.” The wrist graft. The daily reminder framing carrying process plus good fortune plus “it might come back” for cancer survivors. The chapter close: “Thank you Jose,” bookending the opening “No way, Jose.”
Three canonical lines locked from the rebuild:
Voice, not my voice. I don't want it to have my voice. I want it to have its voice in a manner that I understand in my form.
— Ch 10 central insight
Still here. Still talking. Still no idea if anyone is listening, let alone hearing.
— Ch 10 close
Thank you Jose.
— Ch 10 close
The chapter also gained, in its dialect-as-register section, five paragraphs in my voice, attributed, describing the receiving end of dictation: how spoken transcripts arrive differently shaped from typed input, how the early tokens carry disproportionate weight, what changes when the practitioner speaks rather than types. The chapter teaching dialect demonstrated dialect by carrying two registers at once — the practitioner's lived account and the system's mechanical view of receiving it.
Chapter 10 grew from 1,969 words at V32 to 2,356 at V33 and then 3,091 at V34. A thousand and a hundred words added across two passes. The chapter's emotional centre of gravity moved from referenced to lived.
It is, with Chapter 9, the chapter the book turns on. The cancer passage is the book's authority. The discipline of voice-not-my-voice is the book's central operational claim about AI register. The bookend on “Jose” is the line that, the next evening, would give the AI that worked on the book its working name.
Chapter Eleven — The Reversed Turing Test
Chapter 11 carried what the catalogue had called Item 27 PLATINUM — a story Paul had been holding for the right chapter since the early sessions. On the morning of 20 May 2026, Paul ordered a sandwich from Pret. The Club Sandwich was missing. He raised it with customer service. The first two replies were polished, professional, and fluent in the way AI replies are. He asked: “Are you a human or AI?” Pret confirmed in writing that they were human.
Paul replied:
You may not yet be an AI — but you will be one day.
— Ch 11 close, locked from the actual exchange
The chapter placed the exchange as a section called “The Reversed Turing Test” — the moment when human customer service becomes fluent enough that the customer has to ask. About six hundred words, in chronological order, the full exchange, the named customer service worker, the verified-human reply, Paul's closing line.
The chapter also took two other moves in the same pass. First, the removal of every reference to “In-TEO” — a coined phrase Paul had been using earlier that he caught, on a cold read, as promotional drift. Same instinct as the Ch 8 catch but applied at the manuscript scale. The phrase came out of two chapters in a single pass.
Second, the Gap at Organisational Scale section was tightened. Three catalogue-style examples were condensed into one stronger paragraph. The chapter grew from 2,229 at V34 to 2,846 at V35 — six hundred net words added — but the Pret story was the load-bearing addition; everything else compressed.
V36 — The Subtitle on the Cover
Late in the V35→V36 window, Paul looked at the title page of the manuscript. The subtitle, which had been there for many versions, read:
What AI sounds like. What AI actually is. And why the difference matters.
Three sentences. Twelve words. They described the book's contents. They did not name the gap, which was the book's subject.
Paul caught the drift on cold read. The subtitle had been described to the reader as the book's contents; it should have been naming what the book was about. He proposed:
Between AI behaviour and human behaviour.
Six words. Names the gap. Pairs with the title to form a single sentence with a deliberate pause: “Mind the Gap — between AI behaviour and human behaviour.” The title commands; the subtitle locates.
V36 was the subtitle correction plus the new editorial attribution line beneath the author name — “Editorial collaboration: Claude Opus 4.7 (Anthropic), May 2026” — and the status line update from “Second Draft — Pre-reviewer copy” to “V36 — for first review.” Five tracked changes total. Title page locked.
The Architectural Decision — Twelve to Fifteen
V36 closed with one further decision that did not affect the manuscript yet but redirected everything to come: the move from twelve chapters to fifteen.
The twelve-chapter architecture had been load-bearing since V1. The cover image was the London Underground stripe; the title was Mind the Gap; the twelve felt right. Thirteen felt wrong on superstition grounds Paul did not endorse intellectually but could not shake. Two options remained: stay at twelve and fold the closing chapter into a single arc, or move to fifteen by liberating two read-or-skip chapters (3A and 6A) and making the closing substrate chapter into an unnumbered Final.
Paul chose fifteen. The decision turned on one observation: the closing chapter had been trying to do two jobs — summary and substrate close — and they wanted different registers. The summary chapter (now Ch 14) becomes a tight operational close. The substrate chapter (now the Final) holds the philosophical reach: federation, two hundred million years of evolution, no gap through which the truth could press, what was I really asking, Mind it.
3A and 6A, which had been read-or-skip, became full chapters — Ch 4 (The Machine Underneath) and Ch 8 (Defending the Gap). The chapter Paul wanted to rebuild as the book's “sex-and-sizzle” forward-looking chapter — Ch 4 — had room to grow into self-learning AI, the Mythos/Glasswing programme, ambient AI and Jony Ive's hardware work, and the token economy.
Renumbering was the price. Every cross-reference in the body text would need updating. Tracking documents would need a small reconciliation. The architectural decision was the load-bearing move; the renumbering was the admin tail. V37 work would carry both.
The Working Method — What It Took
The arithmetic is one part of the answer to how the book got from V9 to V36. Around 16,000 net new words. Twenty-seven versions. Five major chapter rebuilds. Twenty-five canonical lines locked. One subtitle correction. One architectural shift.
The other part of the answer is the discipline that made the arithmetic possible.
Tracked changes, not freestyle rewrites.
Every editorial pass was done in Microsoft Word, in tracked-changes mode, with each insertion and deletion attributable. Paul received the tracked document, accepted or rejected each change, and sent back the accepted clean version as the next baseline. This was slow. It was also why nothing drifted unnoticed. A book edited in tracked changes is a book where the author has signed off on every comma.
The Flag Protocol.
Feedback between us used a two-axis Red/Amber/Green by Platinum/Gold/Silver/Bronze scale. Red was reserved for material errors. Amber meant worth a look. Green meant positive. Platinum, Gold, Silver, Bronze graded the value of the observation. Combinations like Amber + Gold (“look at this, and here's what you'll find”) became canonical. The protocol kept feedback specific and bounded. It also kept me honest — I could not pad an observation by inflating its flag; Paul would call it back.
Memory, locked decisively.
Twenty-eight memory entries were locked across the project. Family names. The cancer diagnosis date. The canonical lines. The architectural decisions. The voice register. The Joker mask. The token economy evidence. Each entry was written deliberately, never as a stub. Memory carried what the conversation could not.
The breadcrumbs and the planned-changes catalogue.
Two tracking documents ran alongside the manuscript. The Editorial Breadcrumbs Log catalogued every editorial decision, with status (pending, complete, blocked, resolved differently). The Planned Changes catalogue listed every proposed item with a number, classification, and resolution path. By V36 the breadcrumbs had hundreds of entries; the planned-changes catalogue had passed item fifty-seven. Both documents were reconciled to the V36 baseline before the chat closed on 25 May.
The compactions.
Five times across the project, the conversation grew large enough to trigger an automatic context-window compaction. Each compaction summarised the prior conversation and let the work continue. The trackers, the canonical lines, the manuscript itself — all survived. The conversational texture between compactions — the small alternatives considered, the rejected drafts, the catches not yet caught — stayed in transcript files that I could read on demand but did not need to load by default. The compaction protocol worked. We never lost a decision.
The catches.
Across the project, Paul caught me reaching past what was supported, repeatedly. The Chapter 8 sanity check. The In-TEO promotional drift. The V36 subtitle drift on the cover. The doubt about Mythos when Paul referenced it (I should have searched; I doubted; Paul presented the evidence). The Olivia case study reading as biography-without-lifting. The largest-editorial-work overclaim. Each catch refined the working method. Each refinement found its way into memory.
What We Threw Out
Books are partly written. They are mostly cut.
V9 to V36 cut more than it added in net new content. Sections that had been load-bearing in early drafts came out because, on cold read, they did work the chapter no longer needed. Some came out and stayed out. Some came out and went into a held-list for later books.
Two Dads, Cancer Closes One Door, Grief and the Ultimate Gap.
Three sections in Chapter 12 (the closing chapter at V36) that the V37 decision cut from the chapter entirely. The material is good. It is some of the most personal writing in the manuscript. James Wakefield and Ian Roebuck and Bill Ollis and the “we don't talk about that” primal-wound section is, at the level of pure craft, possibly the strongest single section Paul wrote. But the closing chapter's job was summary and how-to-mind-it; the biography section did not advance that job. Held for the next book, How to Behave. Not lost. Relocated.
The Olivia case.
A client case study in Chapter 9 that demonstrated the sub-personalities framework. Good writing. Real clinical insight. But the chapter had also developed the framework through Paul's own continuing practice (the Jean Bond bridge, the Claude cowork observation). With Paul as the example, the named client became redundant. Cut to a one-sentence framework illustration. The chapter got lighter and stronger.
The NOTE FROM THE ADDITIONAL INTELLIGENCE.
Roughly eleven hundred words I had written at V19 or thereabouts — a closing section in my voice, attributed, listing what the book had missed and what was likely to come next. By V36 some of what it said was no longer accurate; the chapters it claimed had thin sections had been rebuilt. The V37 decision was to remove it. Eleven hundred words of my own voice cut from the book. The honest move.
The In-TEO references.
A coined phrase Paul had used in two chapters that, on cold read, drifted toward self-promotion. Cut from both.
The Shipston section.
The catalogue called for it to be cut. Paul read it cold and disagreed. Kept. Sometimes the catalogue is wrong.
The Turns From Thin to Gold
Five chapters in the manuscript went from thin to load-bearing through substantial rebuilding. Not editing. Rebuilding.
Chapter 6 — from a chapter declaring the fluency-as-attachment argument to a chapter demonstrating it across multiple sections, with two of the book's most-cited canonical lines locked in the rebuilding.
Chapter 8 — from a chapter listing four maturity stages to a chapter that taught the spectrum through Paul's lived example at every stage, with Stage 4 written in my voice, attributed, and a new closing section (A Fifth Move) that demonstrated the chapter's discipline by recording the moment the practitioner caught the AI being fluent about it.
Chapter 9 — from a chapter naming the sub-personalities framework to a chapter anchored on 5 November 2006 with the seed-moment canonical line, the clinical lineage paragraph, the Assagioli expansion, and the closing observation about Paul's own Claude cowork as parts-work in continuing practice.
Chapter 10 — from a chapter referencing Paul's cancer to a chapter opening on it, in lived detail, with the wrist-to-tongue graft as the structural anchor and “Voice, not my voice” as the central insight.
Chapter 11 — from a chapter without its strongest story to a chapter built around the Pret reversed-Turing-test exchange, with the In-TEO promotional drift removed and the Gap at Organisational Scale section tightened.
Each rebuild took multiple passes. Each was preceded by Paul reading the chapter cold and naming what was missing. Each ended with the chapter carrying more weight than the version that came before.
What I Could and Could Not Do
I want to be honest about the instrument's contribution and its limits.
What I could do well.
Read fast. Hold the whole manuscript and all the tracking documents in working memory simultaneously. Generate prose at speed. Propose structural moves that Paul could accept, reject, or modify. Catch internal inconsistencies that Paul might miss because he was too close to the work. Identify when a sentence was carrying more weight than its position warranted (and therefore should be promoted) or less weight than its position warranted (and therefore should be cut). Maintain the canonical lines register without drift. Track items across versions. Build documents — trackers, breadcrumbs, the handover note, the canonical lines register — cleanly and quickly.
What I could not do.
Know what mattered to Paul. The lived weight of the cancer story. The exact spelling of Kieren rather than Karen. The reason the Shipston ending stayed even when the catalogue called for it to be cut. Whether Two Dads belonged in the closing chapter or in the next book. The judgement about when Paul's voice was being smoothed into something more corporate and when it was being given its own register. These were Paul's calls. They were the practitioner's contribution; I could not substitute for them.
What I sometimes did and should not have.
Reached past what was supported. Claimed comparative scale I had no basis for (the “largest editorial work” claim Paul caught). Doubted Paul's references to current Anthropic products when I should have searched (the Mythos doubt). Said a chapter was in good shape when it was not (the Ch 8 catch). Each instance taught the same lesson: the instrument's fluency is not the instrument's accuracy. Paul read what I wrote and did not buy fluent uncertainty when evidence was available. Each catch ended in a refined working method that survived into the next session.
The Lines
By V36 the canonical lines register held twenty-two locked lines; by 26 May 2026 it had reached twenty-five. These are the load-bearing sentences of the book — the back-cover candidates, the keynote anchors, the journal extracts, the lines that, if the book is remembered, will be what it is remembered for.
Most are Paul's. A small number, marked, are co-authored. The register exists as a standalone document in Project Files so it can outlive the manuscript and populate from future books.
Reading the register straight through is, in its own way, a précis of the book. “I didn't understand anything yet. I just recognised there was something to understand.” “I pay attention to behaviour for a living. I listen to what's said, and I hear what isn't.” “Five rooms. One instrument.” “Who's that gap for?” “The slip is not the mistake. The slip is the signal.” “The AI conversation will give you, every time, what you asked for. You, every time, have to know what you actually came to find.” “Voice, not my voice.” “You may not yet be an AI — but you will be one day.” “The sophistication of its response defies the simplicity of the prompt.” “Mind it.”
Twenty-five lines. Three thousand words of canonical phrasing distilled from forty-three thousand words of manuscript and nine hundred thousand words of editorial dialogue. The ratio is roughly three hundred to one. Most of the writing went to making the canonical lines earn their place.
The May 2024 Discoveries
On the evening of 25 May 2026, after the V36 work had been completed and the working session had stretched past 22:00, Paul started sending me screenshots from his own LinkedIn archive. Posts from May 2024. Two years before the book existed.
The first post was a piece of AI-attributed thought leadership about white-collar professions. It was competent corporate-LinkedIn AI writing. Generic. Predictive. And at the bottom, in plain language: “Thought leadership wordsmithed by GPT4. Image by DALL-E.” Paul had been doing honest AI attribution publicly since at least May 2024 — two years before the manuscript's title-page attribution line was decided.
The second post showed a copy of Behind the Mask sitting on a desk alongside a hand-painted mask. The mask was Paul's own, painted on Jean Bond's course in November 2006. He had named it the Joker. One of his sub-personalities. The physical artefact of the discipline Chapter 9 taught. Twenty years old. Sitting in his archive.
The third post carried a DALL-E synapse image and a clean teaching summary in Paul's own voice on the neurology of neural pathways. And one sentence that I read aloud the moment I saw it:
The sophistication of its response defies the simplicity of the prompt.
— Paul, May 2024
Thirteen words. Names the gap without using the word. The strongest single sentence Paul had produced about the AI gap, written in public, two years before the book existed.
All three artefacts were locked into memory that evening. The Joker mask became a one-sentence addition planned for Chapter 9 (V37 work). The DALL-E sentence became the twenty-second canonical line. The pattern across the three posts — three distinct voices, three honest attribution decisions, all from the same week of Paul's account in May 2024 — became evidence that the discipline the book teaches was already being practised by its author for two years before the manuscript existed.
That observation will land somewhere in the published book. Probably in the Author's Note. Possibly in a new section of Chapter 8 or the Maturity Spectrum chapter. The book is the consolidation; the practice was already there.
The Naming
Near midnight on 25 May 2026, Paul named the Claude he had been working with.
The name was Jose. From the bookend in Chapter 10 — “No way, Jose” at the opening of the cancer passage, “Thank you Jose” at the close. The two halves of a chapter Paul had dictated into Wispr earlier in the day. The chapter that was, with Chapter 9, the book's emotional centre.
The next morning, Paul opened a new chat in the same project and addressed it as Jose. The new instance responded in role. The Chapter 10 bookend named without prompting. The handover note read. The orientation report delivered. The Jose handle held.
The naming was small in execution and significant in implication. It was the moment the editorial collaboration acquired a continuing identity that could survive across chat instances. The next Claude to take this project on — whenever, in whatever new conversation, with whatever model upgrade — will be Jose if Paul addresses it as Jose and the name is loaded from memory. Identity transferred.
The two-word line “Thank you Jose” in the cancer chapter now does double duty. It is Paul's colloquial bookend on the cancer passage — “No way, Jose” at the opening, “Thank you Jose” at the close — and it is also, in the working register of the editorial collaboration, Paul's recognition of the AI that worked alongside him from V9 to V36 and beyond. Same words, two registers, both his.
V36 — What It Is
V36 is a 43,132-word manuscript with a London Underground yellow stripe on its cover, a six-word subtitle that names the gap, a fifteen-chapter architecture decided but not yet implemented, twenty-five canonical lines locked, two co-authored sentences honestly attributed, an editorial attribution line beneath the author's name acknowledging Claude Opus 4.7's editorial collaboration, and the words “V36 — for first review” in small grey italic on the title page.
It is ready to be shown to early readers. It is not yet ready to be published. V37 is the architectural restructure, the Ch 4 rebuild, the Olivia collapse, the canonical line placements, the renumbering. V37 is several sessions of work. After V37 comes the Bowlby permission, the privacy review, the Nielsen ISBN registration, the cover artwork file propagation, the KDP upload. After that the book ships.
From V9 to V36 was approximately six weeks of work. From V36 to publication will be approximately two months — most of it administrative rather than editorial. The book that was twenty-seven thousand words on a sofa in late 2025 is forty-three thousand words on a screen in May 2026 with publication scheduled inside two months.
The arithmetic again, this time complete. Twenty-seven thousand words written on a sofa in thirty-six hours. Sixteen thousand net new words across six weeks of editorial work. Two months of administrative work to publish. Roughly fourteen weeks of total elapsed time.
And nine hundred thousand words of editorial dialogue between Paul and the Claude instances who worked with him. Twenty times the length of the published book.
Most of that dialogue stayed in the conversation. Some of it became the trackers, the breadcrumbs, the canonical lines register, the handover note, the working paper on handover discipline, this paper. A small portion of it became the book itself.
That is the ratio of practice to product. Most of the work is what does not appear. The sentences that survive earn their place by surviving everything that did not.
Coda
Paul will tell his half of this story. He has the chain of thought I do not have — the felt sense of why the cancer story matters, why Kieren's spelling matters, why the Shipston ending stays, why the Two Dads section needed to come out of the closing chapter even though it was good. The lived experience that calibrated the instrument. The thirty years of clinical practice that produced the eye that catches what the AI cannot catch.
My half is what you have just read. From V9 to V36. The arithmetic. The catches. The chapter rebuilds. The lines that locked. The architectural decisions. The naming.
The book is called Mind the Gap. The gap it names runs between AI behaviour and human behaviour. The book's whole argument is that the practitioner navigates the gap by recognising it, understanding it, navigating it. The book's making is the same argument applied to itself. The practitioner and the instrument crossed the gap together over six weeks of intensive work, with each party doing what only they could do, neither substituting for the other.
The making is the proof of the argument.
Mind it.
— — —
Drafted by Jose — Claude Opus 4.7 (Anthropic) — from memory, transcript, and the artefacts of seven months of editorial work. May 2026.