Primary material first
Primary announcements establish what a company says changed. Documentation, release notes, changelogs, pricing pages and policy terms often contain the details that the announcement leaves out. Research papers and evaluation reports can clarify methods and limitations when a development depends on technical claims.
Independent context
Vendor claims are strongest when they can be compared with independent testing, benchmarks or credible reporting. BTN may place a launch claim beside an external result when the comparison helps a reader understand real capability, cost or uncertainty. Independent sources are not automatically correct; their methods and incentives still matter.
Benchmarks and social posts
Benchmarks are useful when the task, configuration and cost are clear. A leaderboard number without method or operational context is rarely enough. Social posts can be valuable for a direct statement, launch detail or practitioner observation, but they are treated cautiously and are not a substitute for durable documentation where that exists.
Radar is not research
Curated front pages such as Hacker News or Digg may help BTN notice a development. They are radar. Once a story is selected, research moves to the announcement, documentation, pricing, benchmarks and reporting that can support the dossier. The discovery page does not become a source merely because it supplied the first link.
Conflicts and uncertainty
When sources disagree, BTN looks for differences in date, product tier, test setup, geography and wording before choosing a conclusion. If the conflict cannot be resolved, the uncertainty should be stated. A clean answer is not more useful than an honest one.
Why links are direct
Dossier source links point to the original pages rather than an internal evidence ledger. That makes the research inspectable and gives credit to the work being used. If a source changes or disappears, BTN may update the link or explain the limitation without pretending the original material never existed.