1. Write down the exact claim
Verification starts with a sentence specific enough to be wrong. “The update supports Linux” is more useful than “The product is better now.” Record the product version, date, location and other qualifiers that would change the answer. Split a sentence containing several assertions into separate claims.
Decide what evidence would establish each part. An official release note can establish what the vendor announced. It does not prove that every installation works. A user report can establish that someone described a problem; it does not establish how common the problem is.
2. Trace the answer back to original material
Use Kruqond to search the claim and ask for original documentation, reporting or records. Follow the citations rather than treating their presence as proof. Prefer a direct statement, document or observation relevant to the claim over a page that merely repeats another summary.
Several articles may all depend on one announcement. Count the underlying evidence, not the number of pages repeating it. A company’s own page is useful for its published prices or product terms, while claims about real-world performance may need independent evidence.
3. Read past the headline and the quoted line
Open the cited URL and check that it resolves to the intended document. Read the surrounding paragraph, footnotes and date. Look for corrections, revisions and definitions. A headline can omit a condition that changes the meaning of the result.
Match the source to the exact claim. A source may show an announcement date but not an availability date, a correlation but not causation, or a result for one tested version rather than every version. Screenshots and reposted clips are leads; find the original context where possible.
4. Look for evidence that could change your conclusion
Search for a correction, a newer document or an informed disagreement. If two sources conflict, compare their dates, methods and scope before choosing one. A newer page is not automatically more accurate, and a source with no date may require extra caution.
Keep an evidence ledger with the claim, source URL, publication or revision date, relevant passage, what it supports and what it does not. Use a retrieval date when the source has no visible publication date; do not invent a publication date from it.
- Check whether the evidence is first-hand or repeats another source.
- Identify the qualifiers required for the claim to be true.
- Look for a correction or a credible counterexample.
- Mark inaccessible, ambiguous or conflicting evidence explicitly.
5. Publish a conclusion with the right scope
Use plain labels such as supported, contradicted or unresolved, then explain the scope in a sentence. Link the evidence next to the statement it supports. Keep an inference visibly different from a direct finding, and avoid a confident verdict when key evidence is missing.
Kruqond citations help you return to retrieved sources; they do not guarantee that the answer interpreted them correctly. For a consequential decision, the final check remains the original evidence and the appropriate domain expertise.