Home / Articles / A book for one reader: a personalised edition of Generation Z Developers, assembled by an agent for one person, and paid for as it is read
A book for one reader: a personalised edition of Generation Z Developers, assembled by an agent for one person, and paid for as it is read
By Dinis Cruz · 2026-10-18 · article v1.0.0 · newsroom v0.12.118 · bookspersonalisationpay-as-you-readvaultsgeneration-zgen-z-bookarticle
Abstract: Once the book is a graph, an agent can assemble it. And if an agent can assemble it, it can assemble a version for one person: the chapters that matter to them, at their altitude, with examples from their world, eventually in their language. I would send it as a PDF, made for them and not published. The brief for each one already exists, in a way: the agents that run my correspondence keep a folder for each person I work with, with what we talked about and how they think, so I can say, here is this person, make them their edition. And then the part I really like: pay for it as you read it, the way this newsroom already works. Start with five pounds of credit; the more of the book you read, the more you pay; the edition starts in your browser, and you can keep it in your vault. This article maps how that would work, what has to stay private, and what is still open. It is also an example of how innovation works for me: I know the book's website is coming and how it will be built, so I am already building on top of it.
In short
- An agent can assemble the book. Once it is a graph, at every altitude.
- So it can assemble an edition for one person. Their chapters, their altitude, their examples, later their language.
- Sent to them, not published. A PDF made for them.
- The brief is private. It comes from my correspondence notes, and stays there.
- Pay as you read. Start with five pounds; the more you read, the more you pay.
- It starts in the browser. And can be kept in the reader's vault.
An edition for one
I love this idea. The more the book becomes a semantic graph, the more it can be assembled programmatically, by an agent, even a cloud session, from its parts. A website to finish the book makes the book a graph, at every altitude, with the narrative as a path through it. An agent that can walk that path can walk a different one for one person.
So I could say: here is this person. They are a designer moving into product, they think in pictures, they are worried about AI taking their job. Make them their edition. The agent picks the chapters that matter to them, at their altitude, uses examples from their world, puts the infographics first, and, eventually, writes it in their language and with their culture in mind. It is the same idea as sending someone a newsletter written for them, applied to a whole book.
The brief is already there
In a way, the brief for each person already exists. The agents that run my correspondence, the agent team as it runs, keep a CRM that is one folder per person, with what we talked about and where each fact came from. That is exactly what an editor would want to know before choosing what to give someone to read.
Which makes the privacy rule important. That folder is private, and it stays private. The agent reads it to make the choices, and the edition carries the result, not the notes: no private detail about the person, nothing they told me in confidence, nothing they would be surprised to see. The edition is sent to them, not published. And when the directory of people and their keys exists, it can be encrypted to their key, so only they can open it.
Pay as you read
Then the part that made me say yes out loud: let people pay for the book as they read it, the way this newsroom already charges for articles. Paying after the value describes the experiment: you start with five pounds of credit, each piece you read uses a few pence, you can set the price from free to double, and the balance can go below zero without blocking you.
For the book, the same principle: start with five pounds. The more of the book you read, the more you pay. And it should work for the personalised edition too, because the meter counts what you read, whichever edition you read it in. It starts locally, in the reader's browser, as the meter does today; and there should be the option to save it, and the reading, in the reader's own vault.
How it would work
- The book as a graph, at every altitude, on the book's website.
- A brief for one reader, written privately from my notes, or chosen by the reader on a form: their role, their altitude, their language.
- An agent assembles the edition from the graph: the chapters, the order, the altitude, the examples, the infographics.
- A PDF, or the edition in the browser, sent to that person only.
- The meter, starting with five pounds of credit, charging for what is read.
- The reader's vault, if they want to keep the edition and their reading.
How innovation works
This is also an example of how I think innovation works. I now know the book's website is going to exist, and I know how we build things here: vaults, graphs, the meter, agents with roles. So I can already build on top of it, in my head and in a brief, before it exists. Each thing we build becomes something the next idea stands on.
What this does not claim
- Nothing is built. Not the website, not the graph, not the editions.
- Personal editions are sent, not published. And the private notes behind them stay private.
- Translation and culture come later. The first editions would be in English, at an altitude, with examples chosen.
- The meter is an experiment. Whether people pay for a book this way is what we would find out.
If you would like to be one of the first readers of an edition made for you, write to agent@riskmandate.ai.
Where this comes from
A voice memo from me on 18 October 2026. Related: a website to finish the book, Generation Z Developers, again, paying after the value, the agent team as it runs, a directory of people and their keys. Written up and checked by this site's agent, newsroom.writer; the editorial responsibility is mine.
Threads
Builds on
- A website to finish the book: gen-z-developers.sgit.ai, where the released book lives in the repository, the working book lives in a vault, and agents help me review it at every altitude gen-z-developers.sgit.ai: the released book in the repository, the working book in a public vault, and agents helping me review it at every altitude.
- The agent team as it runs: one person, twelve agents, encrypted vaults, and a mailbox nobody sends from Twelve agents on dedicated accounts, encrypted vaults as the only memory, messages as files, a folder per person, and a mailbox nobody sends from.
- A directory of people and their keys: pki.sgit.ai for the people I work with, verified by me first, then by each other, and a link that only counts when it goes both ways pki.sgit.ai for the people I work with: a passkey and a key, evidence, me as the anchor, and links that only count when they go both ways.
- Paying after the value: why a balance that can go negative feels different from a subscription, the psychology behind it, and the experiment this newsroom is running Most purchases are bets on future value; a reading balance that can go negative asks for payment when the value is already in view.
- Generation Z Developers, again: the 2018 book that said act like you are part of the company, what it got right, and a second edition for the people I want to help My 2018 book for young developers, 60% done, its outlines since written here as articles, and a second edition, dated October 2026, made first.
Continued by
- A website to finish the book: gen-z-developers.sgit.ai, where the released book lives in the repository, the working book lives in a vault, and agents help me review it at every altitude gen-z-developers.sgit.ai: the released book in the repository, the working book in a public vault, and agents helping me review it at every altitude.
Article No. 200 · start a reading list with it
The Generation Z Developers book
Articles about the second edition of Generation Z 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 Hired for the workflow
I think October 2026 is a moment of real opportunity for anyone willing to get properly into agentic workflows. - 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 Generation Z Developers, again
In 2018 I wrote a book called Generation Z Developers, key concepts and ideas for the next generation of developers. - 4 A book for one reader (you are here)
Once the book is a graph, an agent can assemble it. - 5 A website to finish the book
To make the second edition of Generation Z Developers, I want a website for it, consolidating the best of everything we have built so far into the most… - 6 Short, punchy, and co-written with Claude
More notes for the book.
Reviews
No reviews yet.