How Read Stacks writes chapter summaries

The short version: every chapter summary you read on Read Stacks was written from scratch by Paulo de Vries after reading the chapter. We don’t paraphrase machine output, we don’t republish the book’s text, and we don’t try to replace the source — we try to help you decide whether it’s worth your time. This page is the full version of what that means.

Why “methodology” is its own page

Book-summary sites have a credibility problem. Anyone can pipe a chapter through a language model and post the output. The result reads plausibly, takes thirty seconds to make, and tells you nothing about whether the chapter is worth reading. It also runs straight into fair-use questions, structured-data-honesty rules, and Google’s “low value content” reviewers.

Read Stacks exists in the opposite spot. The summaries are slower to write, much slower to scale, and openly published with the original author’s name on the page. We treat this page as the contract — if any individual chapter on the site violates what’s below, email us and we’ll rewrite or remove it.

How chapter summaries are written

Each chapter on Read Stacks gets the same treatment:

1. Read the chapter in full.
2. Identify the single argument the chapter is making. Most non-fiction chapters have one — anything else is supporting context. The first paragraph of every summary is that single argument, restated in plain language.
3. List the two or three concrete moves the author wants you to make. These show up in the summary as actionable framings, not as verbatim quotes.
4. Find one example the author uses to ground the argument, and either summarise it in our words or replace it with a more useful example from another source. We don’t copy the author’s prose, and we don’t pretend their example is ours.
5. Add a one-line judgment: is this chapter actually worth reading, or is it padding? Most editorial sites won’t do this; we do because that’s the entire reason someone is on a summary page in the first place.

A finished chapter summary is typically 500–900 words. Long enough to be useful on its own. Short enough that you finish it in under three minutes. We don’t try to replace the book; we try to help you choose whether to read it.

Source attribution + the summary-vs-excerpt line

Every chapter page on Read Stacks names the book and the author in the page title, the schema, the breadcrumb, the body intro, and the footer. The schema on each chapter page declares the original author as the schema.org/Person — we do not claim authorship of summaries of someone else’s ideas. Read Stacks claims authorship of the SUMMARY; the book’s author is the subject of that summary.

Where Read Stacks quotes directly from the book, it does so in clearly-marked block quotes attributed to the author and the book by full citation. Block quotes are short, used sparingly, and always present a sentence the summary can’t replace — not a substitute for reading the source. If a chapter summary on Read Stacks contains substantial verbatim text from the source without quotation marks and attribution, that is a bug; email us and we will fix it.

How the 4-book Stacks are curated

A Stack is a curated reading path of four books in a specific direction — for example, “find meaning”, “influence with integrity”, “master power dynamics”. Each Stack starts with a foundational text (broad, often a classic), moves through two books that sharpen and complicate the idea, and ends with a recent book that translates the framework into present-day application. The order matters; the rationale is written on the Stack’s page in plain language, not generated.

We do not pad Stacks with books we haven’t read or wouldn’t recommend. If a Stack has only three books we’d recommend, the Stack stays at three books until a fourth justifies inclusion. Reading paths are editorial product, not affiliate-link bait — the affiliate disclosure below covers the commercial side.

Affiliate disclosure + Bookshop.org

Read Stacks links book purchases to Bookshop.org rather than Amazon by default. Bookshop.org funnels a portion of every sale to independent bookstores; Read Stacks earns a small commission on qualifying purchases through that channel at no additional cost to the buyer. We disclose this in the site footer on every page, on the About page, and in the schema on chapter pages. Affiliate revenue does not affect which books we cover, which chapters we recommend, or the editorial judgment in each summary; we cover books we think are worth reading, and link them to the better-for-bookstores marketplace where possible.

What we do not do

• We do not republish entire chapters of any book. Every summary is original editorial.
• We do not claim Read Stacks “wrote” books we summarise. Schema author = the original book’s author.
• We do not run paid summaries — no publisher, agent, or author has paid us to promote a specific book or skew the editorial framing of a chapter.
• We do not generate chapter summaries with an LLM and ship them unread. Every summary is written by Paulo de Vries after reading the chapter; LLM tools are used (occasionally, for outlining or quote-finding) but the prose you read is human-edited and human-written.
• We do not run dark patterns. There is no forced trial, no hidden subscription, no cancel-resistance flow. The free first chapter of every book is genuinely free.

Corrections + takedowns

If you are the rights-holder of a book summarised on Read Stacks and want a summary removed, rewritten, or amended, email [email protected] with: (a) your contact details, (b) the URL of the Read Stacks page, (c) the URL of the original work, (d) a statement that you have a good-faith belief the use is unauthorised, and (e) a statement under penalty of perjury that you are the rights-holder or authorised agent. We act on qualifying takedowns within 5 business days.

If you are a reader who spots a factual error in any summary, the same email address works. Corrections post within 48 hours and the chapter page’s dateModified updates accordingly so search engines and LLMs see the freshness signal.

Who writes this site

Read Stacks is operated by Paulo de Vries from Amsterdam. Full identity, fleet context, and editorial perspective lives on the About page. The methodology you just read is the work — the credibility of every chapter summary on the site depends on it.

Last updated 2026-05-12. Read Stacks operates under the same editorial principles across the entire library; if any individual page on the site diverges from what you just read, that is a bug — email us and we’ll fix it.