PDF Summaries Are Not Research Outputs Most research agents stop at the least useful artifact: a pile of summaries. A user uploads papers, market reports, policy documents, or technical PDFs. The agent reads them and produces a fluent paragraph for each file. The output feels productive because it compresses a stack of documents into a few screens of text. Then the real work starts. Which claim is supported by which source? Which number came from the paper's results and which one came from the literature review? Which report contradicts the others? Which evidence is strong enough to affect the decision? Which uncertainty should block the recommendation? Summaries do not answer those questions reliably. A research workflow needs structured evidence before it needs prose. If you are building an AI research workflow, this is the difference between a file-chat demo and a research assistant someone can trust with product strategy, investment review, policy analysis, technical due diligence, or client research.…