Research and corrections policy

How the research works

1. Resolve the product identity and retain the official website before evaluating product claims.
2. Prefer official documentation, API references, pricing pages, changelogs, status pages, and vendor-owned repositories.
3. Label vendor claims, documented facts, and editorial assessments separately.
4. Record a checked date and state missing evidence as not retrieved, never as proof that a feature does not exist.
5. Do not claim runtime testing unless the product was actually run. The current directory research is document-based.

Alternatives-page policy

Competitive sets are editorial classifications, not rankings. Each set exposes its membership test and exclusions. A page may publish only when it has a researched anchor, at least 300 words, and more than 40 percent corpus-unique six-token shingles after global navigation and footer text are excluded.

Official links on these pages are a page-level source set unless a claim names a more precise source. The Lab does not present page-level links as field-by-field verification. Pricing appears only when the retained record says official pricing was retrieved.

Editorial review and corrections

Programmatic pages pass automated route, metadata, schema, internal-link, source-count, punctuation, word-count, and uniqueness checks. Representative pages from every competitive set are then reviewed for clarity, fairness, evidence labels, and visible research limits before publication.

If a source changes or a statement is wrong, send the exact page URL and correction through theCheetah contact form. The research team checks the official source, updates the retained record and checked date when warranted, then reruns the same publication gates. Material corrections are not silently converted into new claims.

Ownership and team background are available on the About Cheetah page. Research questions can also start in the Systems Lab help guide.