Shree Mandadi, April 2026, continuous.engineering

This book started as a decision, not a thesis. I chose not to renew an analyst's contract once AI tooling had absorbed the role. It was the individually rational call. It was also the moment the pattern stopped being abstract to me.

Since then I have watched every senior operator I know make versions of the same decision, for the same rational reasons, one quarter at a time. None of us set out to stop developing the next generation of judgment. We each made a defensible call, and the defensible calls added up to something none of us would have chosen on purpose.

The cost of the pattern is not yet legible. This book is an attempt to make it legible, and to give operators who recognize it a way to act on it that survives a tight quarter.

It was developed publicly across an 11-week LinkedIn article series starting April 2026, in the open, before it was a book.

Written plainly, the same way the rest of this site discloses AI and commercial ties.

01

Commercial ties. continuous.engineering licenses the Succession Governance Policy (Appendix A of this book) to organizations directly, and runs vMentor, a real site service for executive mentorship. Both are referenced in this book because they are the practical answer to the problem it describes, not because the book exists to sell them.

02

AI co-authorship. This book was written alongside Claude, Anthropic's AI assistant. The arguments, the frameworks, the examples, and the position taken in every chapter are mine. The fluency, the research synthesis, and a meaningful share of the drafting are Claude's. That division of labor is disclosed here in the same terms as the rest of the site's AI Disclosure page, because a book arguing against quietly absorbing judgment into a tool would be dishonest if it hid its own use of one.

Four honest paths through it. Pick the one your week can afford.

20 minutes

The front matter, plus the two sections that make the whole argument

Front matter, Section 1.1, and Section 10.6. Enough to know whether the argument applies to you, and what it would ask of you if it does.

2 hours

The spine of the argument

Chapters 1, 2, 4, and 5. The tax itself, why it's individually rational and collectively catastrophic, and the first two moves toward reversing it.

A weekend

The whole book, in order

All 11 chapters plus appendices, read as written. The full case, the counterarguments it takes seriously, and the policy it ends on.

Implementation

Skip straight to the toolkit

The appendices on their own: a board-ready Succession Governance Policy and the reference cards that operationalize it, for a reader who already believes the argument and wants the mechanism.

Eleven chapters, five appendices.

Chapter 1

The Missing Generation Tax — why every AI-leveraged founder is quietly borrowing from 2035.

Chapters 2–10

The mechanics of the tax, why it compounds silently inside an organization that looks healthy on every quarterly metric, the coordination failure that keeps any single operator from unilaterally fixing it, and the specific practices — Proximity Dose, Reinvestment Rate, being visibly wrong on purpose — that reverse it without asking anyone to be less efficient with AI.

Chapter 11

What this costs you and what it costs the people after you, laid side by side.

Appendix A — Succession Governance Policy

A board-ready policy: what to measure, what to publish, and what a board should ask a management team that cannot answer it.

Appendix B — The Pledge

The manifesto itself, live on this site since before the book: read and commit to it here. Signing it is the first commitment the book asks for.

Appendices C–E

Reference cards: the Proximity Dose worksheet, the Reinvestment Rate calculation, and a one-page version of the argument for a board packet.

Appendix F

Contact. Questions about the policy, licensing it for your organization, or vMentor engagements: continuous.engineering/contact.

Ask Maya about licensing the Succession Governance Policy, or sign the pledge yourself.

The book makes the case. The policy is what you'd actually run. Maya can walk through either, or point you to vMentor if the fastest fix is a mentor, not a document.

Sign the pledge →