How to ask AI about a whole book — and why pasting it in is not enough

To ask AI a real question about a whole book — where the argument turns, what the author walks back, whether chapter nine contradicts chapter two — the AI has to read the book the way you would: look at the table of contents, decide which chapters the question needs, read those in full, and go back for another if the first did not settle it. Pasting the whole book in and searching chopped-up fragments both fail at exactly these questions.

Every AI reading tool has to decide what happens when the material is longer than the model can handle well. That decision is invisible in the answer, and it determines whether the answer can be trusted.

Option 1: paste the whole thing in

Context windows are now large enough to hold many books, so this sounds like the obvious fix. It has two problems.

Fitting is not the same as attending. Research on long contexts — the best-known paper is titled Lost in the Middle — found that models recall material at the start and end of a long input far more reliably than material in the middle. A book pasted in whole is mostly middle. The answer will be fluent, and it will lean on whatever was easiest to see.

It is expensive every time. Every question re-sends the book. Ten follow-ups cost ten books.

Option 2: chunk it and retrieve

The standard pipeline cuts the book into fragments, finds the ones most similar to your question, and answers from those. For "what year did the author move to Paris?" this works well.

For questions about the book as a whole, it fails quietly. "Where does the author change position?" has no single fragment that matches it; the evidence is spread across chapters. "What does this book never address?" has nothing to match at all. And the answer gives no sign that the decisive passage was never retrieved.

Option 3: read it like a reader

What a person does with a book they have not read is neither of the above. They look at the contents, pick the chapters the question is about, read those properly, and flip back when something does not add up.

That is the approach MindMax takes:

1. Structure first. The chapter map comes from the table of contents the book was published with — or, for PDFs without bookmarks, from the headings — so the book can be navigated by its own structure.
2. Whole sections, not fragments. Once a chapter is chosen, it is read in full, with its structure intact.
3. Go back if needed. If what was read does not settle the question, another chapter is opened.
4. Say what was read. Every answer lists the sections it actually read, so "the book does not say" and "it did not look" are never the same answer.
5. Quote it. Every claim carries a verbatim quote that opens on the passage in the book.

Documents short enough to read whole — most papers, reports and single chapters — are simply read whole. The navigation only starts when the material is bigger than the model can attend to well, and that line is drawn well below what the model technically accepts.

What this does not fix

• Badly built books. If the chapter metadata is broken, or the whole book is one giant file, there is no structure to navigate. The book still reads; whole-book questions get harder.
• Questions that need every page. "Count every mention of X" is a search job, not a reading job — use search inside the book for that.
• Judgement. Reading the right chapters gets you an answer grounded in the book. Whether the book is right is still your call.

What is not claimed

We have not published a benchmark comparing these approaches, and we are not going to quote one we have not run. The argument here is about failure modes: pasting in hides attention loss, retrieval hides misses, and reading by structure — with a list of what was read — makes its own gaps visible.

---

The concept in full is full-text-first answering; the why-no-vector-database side of it is in why there is no vector database in it. For books specifically, see the AI EPUB and Kindle reader.