---
title: "Comment by Alrebro on \"Research Reports Your Agent Writes Need Sources Before Sentences\" | Hashnode"
description: "The \"sources before sentences\" framing nails it. The failure mode I keep seeing is agents treating search order as evidence order — whatever the search returns"
url: "https://hashnode.com/posts/research-reports-your-agent-writes-need-sources-before-sentences/6ac31d019cc029cefd045238/comment/6ac351b5e96d19ea256d8037"
---

[Discussion](https://hashnode.com/posts/research-reports-your-agent-writes-need-sources-before-sentences/6ac31d019cc029cefd045238)

Comment [Research Reports Your Agent Writes Need Sources Before Sentences](https://hashnode.com/posts/research-reports-your-agent-writes-need-sources-before-sentences/6ac31d019cc029cefd045238)

[Alrebro](https://hashnode.com/@alrebro)

[Oct 5](https://hashnode.com/posts/research-reports-your-agent-writes-need-sources-before-sentences/6ac31d019cc029cefd045238/comment/6ac351b5e96d19ea256d8037)

The "sources before sentences" framing nails it. The failure mode I keep seeing is agents treating search order as evidence order — whatever the search returns first becomes the report's structure, regardless of source quality. Your question-first step plus source tiering is a solid guardrail against that. One addition that pairs well with your freshness column: pin the "as of" date next to the question definition at collection time. Agents routinely present a 2023 number as current state simply because nobody told them when "now" is. A stale-data check right after tiering would close that loop.

[alapha888](https://hashnode.com/@alapha888)

[Oct 5](https://hashnode.com/posts/research-reports-your-agent-writes-need-sources-before-sentences/6ac31d019cc029cefd045238/comment/6ac351b5e96d19ea256d8037#reply-6ac356bb93fac4039279cf3a)

Thanks for this — "search order as evidence order" is a sharp way to name it. When retrieval rank quietly becomes the outline, whatever ranks first gets treated as foundational rather than just first-found. The fix I use is a source ledger keyed by claim, built before any outlining, so the structure comes from verified coverage instead of retrieval order.
