Research literacy hub
Research-literacy guides for better evidence reading
Good decisions start with better questions. These guides explain how to separate a document, a study record, a result, and a marketing conclusion.
Why research literacy belongs on a verification site
A code check answers a narrow commercial question. It does not answer whether a broader claim is scientifically established. The fastest way to improve information quality is to help readers recognize the difference between a source, a claim, and an inference.
The guides in this section concentrate on reading methods: locating a primary record, checking dates and study design, reading a certificate without overstating what it proves, and noticing when an assertion goes beyond the evidence linked beside it.
A deliberately non-promotional scope
This guide library is not a buying guide, treatment guide, or dosing resource. It avoids prescriptive medical instructions and product recommendations. Instead, it points to public evidence resources and explains the questions a careful reader can ask.
That boundary is essential. Search pages that blend product promotion with therapeutic certainty are less useful to readers and less defensible when reviewed closely.
Choose a guide by the question in front of you
Use the source-search guide when a page gives a citation but not the original record. Use the trial-literacy guide when a claim rests on a study registration or a completed trial. Use the lab-report guide when a document is presented as a quality signal but its identity, date, lot relationship, or analytical scope is unclear.
The evidence-hierarchy, uncertainty, funding, and peer-review guides handle a different problem: how much weight a reader should place on a document once it has been located. Keeping these questions separate makes the library more useful than a generic collection of research vocabulary.
Reading methods are more useful than conclusion shopping
A guide library should not be a collection of terms that readers use to find the answer they prefer. Its job is to make the route from question to evidence visible: first identify the claim, then locate the document, then inspect the design or record, and only then decide what the document can support. That sequence works for research pages and for a cart observation, even though the source types differ.
The guides are arranged by the obstacle a reader faces rather than by a promise they are meant to validate. Some explain how to locate a paper, some explain why a registry is not a result, and some explain how to read an order total or gateway label. That organization encourages readers to preserve uncertainty where it belongs instead of treating a single page as a shortcut to certainty.