for agents/llms.txtv0.14.29

Home / Articles / 143 notes in a day: how my pen on a printed release candidate became a record, decisions with their provenance, a review hub and a plan for the next candidate, read by agents

143 notes in a day: how my pen on a printed release candidate became a record, decisions with their provenance, a review hub and a plan for the next candidate, read by agents

By · 2026-10-31 · article v1.0.0 · newsroom v0.14.29 · gen-z-bookbooksreviewhandwritingpaperagentsprovenancearticle

Abstract: On 19 October I printed release candidate 2 of my book, Generation ZX Founders, 168 A4 pages, spiral bound, and read the first 19 pages in a café with a pen. I photographed the pages in four batches and sent them to the book's team of agents. By the end of the day my 143 handwritten notes had become a record: each note typed word for word, with where it sits on the page and what it means, and each page drawn three ways, my photograph with numbered callouts, the page redrawn with my marks in place, and a sketch of the page after the change. Where the agents could not read my hand, 11 times, they did not guess; they asked, and I answered by voice. Four of the notes were decisions, and the book's decisions page records them with their provenance: decision 016, a release candidate is a release, sold now, made in pen on page 4; decision 017, it is a new book, not a second edition, made in pen on page 9, where I circled "new book"; decision 018, every candidate has two editions, the release and the review, from a note that says we need two; and the title itself grew in the margins. My pen asked for a lot: the voice above all, 32 notes on it; meeting the reader where they are; drawing what the text only describes; facts marked apart from opinions; and QR codes in the margins. When I asked whether all the pages were being tracked, they were not, so the agent built a review hub where every note has its own address. I wrote about the habit in Reading with a pen again. This is what the agents actually did with the notes, and what it shows: a handwritten review can be as traceable as a pull request.

Page 9 of the printed release candidate: my notes, numbered, read word for word and explained beside the page.

In short

A café, a pen and 168 pages

The printed release candidate on a café table, 19 October 2026, with the pen.

On 19 October I printed release candidate 2 of my book, Generation ZX Founders, 168 A4 pages, spiral bound, and sat in a café with a pen. I read the first 19 pages and marked them as I would any book I care about: underlines, boxes, arrows and notes in the margin. I photographed the pages in four batches, out of order in one case, and sent them to the team of agents that works on the book.

In Reading with a pen again I wrote about the habit: reading has three moments, and the agents now do the third, processing what you marked. That article was written that day, when the review had reached 83 notes. This one is about what the agents did with all 143, from the book site's own four-part record.

Reading the hand

The agents did three things with every page.

My handwriting is not easy. That the agents read 143 notes and asked about only 11 is the part I still find remarkable.

What the pen asked for

Page 15: the pen asks for Wardley maps before graphs, and for the case to be drawn, not told.

The themes grew batch by batch, from five on the first three pages to thirteen by page 19. In the record, the largest are:

And the pen said what works, too: six ticks on one batch alone, "exactly", "these are great :)", and "this needs to be a common theme across the book". On page 9, after eight pages of asking for more: "Finally we tell the reader why they should read this book :)".

When a margin note is a decision

Some notes were not edits. They were decisions about the book, and the book's decisions page records them with where they were made:

That is the part I find most useful. A decision made with a pen on paper is usually lost, or remembered as a vague intention. Here it has an id, a date, the page it was made on, and the note that made it.

The page asks for room

The margin system the agents sketched from my notes: fact and opinion marks, and working QR codes.

Two of the requests changed what a page of the book can be. The fact-or-opinion notes led to a margin system that marks a claim as fact, with its data, or as my opinion. And the QR-code notes led to codes in the margin that work: the agents' sketch has seven, each resolving to the book's site through a short address, so a printed page links to what the paper cannot hold. That idea has since grown into the augmented book.

The view I asked for

Partway through the fourth batch I asked whether all the pages so far were being tracked. They were not, so the agent built one: a review hub with all 19 pages and 143 notes, which can be filtered by theme and chapter, where every note has its own address, so a single note can be linked from a decision, a brief or a reply. The build now refuses a batch with no article, or notes that are not numbered one to the last. A view that was missing became a rule that keeps notes from being lost.

What it shows

A handwritten review is usually the least traceable kind there is: marks on paper that the author reads once and forgets. Here it became as traceable as a pull request: every comment recorded, every reading checked, every decision linked to the note that made it, and every page drawn as it would look after the change. The pen stays the best way I know to think while I read. The agents make what it writes count.

Where it stands

The review stopped at page 19 of 168. The agents planned the changes, chapter 1 paragraph by paragraph and chapters 3 and 4 swapped among them, but there is no third candidate yet: my focus moved to the book of the talk, which is using the same method. When I come back to this book, the record is waiting, note by note.

What this does not claim

Where this comes from

Peer review Not reviewed yet. Review it

Threads

Vaults & methodGraphs & knowledge This article as a graph →

Builds on

All articles · All graphs

Article No. 353 · start a reading list with 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

Generation ZX Founders (GenAI Edition)

Articles about Generation ZX Founders (GenAI Edition), the new book that grew out of Generation Z Developers (2018), first called Generation ZX Developers: the ideas going into it, and how it is being made. Every article tagged gen-z-book joins this list, in the order it was published.

  1. 1 Hired for the workflow
    I think October 2026 is a moment of real opportunity for anyone willing to get properly into agentic workflows.
  2. 2 Act as the job you want
    This is the advice I end up giving most often to people I know who are looking for a job.
  3. 3 Generation Z Developers (AI edition)
    In 2018 I wrote a book called Generation Z Developers, key concepts and ideas for the next generation of developers.
  4. 4 A book for one reader
    Once the book is a graph, an agent can assemble it.
  5. 5 A website to finish the book
    To make Generation Z Developers (AI edition), the plan is a website for it, consolidating the best of everything we have built so far into the most productive…
  6. 6 Short, punchy, and co-written with Claude
    More notes for the book.
  7. 7 Discovering the book
    On the evening of 18 October the repository for the book's website was empty.
  8. 8 A pull request by another name
    This morning I am reading the printed release candidate 2 of Generation ZX Developers, with a pen.
  9. 9 Can you sell it? Start selling what you have, however rough it is, because the point is not to sell, it is to learn
    One of the most important pieces of advice I can give any founder is to start selling, now, what you have.
  10. 10 Start a company
    If you are an entrepreneur, start a company, as soon as you have a bit of revenue to put through it.
  11. 11 You are a developer, you just do not call it that
    Every GenAI founder I know is a developer, and none of them think so.
  12. 12 Reading with a pen again
    I buy a lot of books, because a book is a better medium for me than a screen, and what people call its inefficiencies are its best features:…
  13. 13 Fund it with time
    How do you fund a startup?
  14. 14 Open source what you build, even while you are employed
    People worry that if they open source their ideas, others will copy them.
  15. 15 When the customer becomes the commodity
    When you draw a Wardley map of your business, ask where your customer sits on it.
  16. 16 The graph companies
    Something I have been looking at while reading my book: some of the biggest and most successful companies in the world are graph companies.
  17. 17 The jobs that never scaled
    In the book I say that the opportunity is not only in new jobs, but in jobs we have done for a very long time that never really…
  18. 18 Programming, taught upside down
    In the book I quote Paul Lockhart's A Mathematician's Lament: if you set out to design a system that destroys a child's curiosity about maths, you could not…
  19. 19 Connect your dots backwards
    The book has a chapter called Connect the dots backwards, after Steve Jobs's line that you can only connect the dots looking backwards.
  20. 20 143 notes in a day (you are here)
    On 19 October I printed release candidate 2 of my book, Generation ZX Founders, 168 A4 pages, spiral bound, and read the first 19 pages in a café…

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.