Evidence and provenance
We prefer a clear Unknown over a confident guess.
CurioBeam records where product claims came from, separates assertions from normalized facts, and keeps future or preview capabilities distinct from what is currently available.
Sources
What counts as useful evidence
We prefer first-party sources such as official product websites, documentation, app-store listings, repositories and licenses, pricing pages, and attributable maker statements. Direct testing or editor observation can also be useful when the claim can be bounded.
Third-party directories and search snippets may help us discover a product, but they are not automatically treated as canonical proof.
Destination safety
Official links are checked separately
CurioBeam tries to distinguish an official destination from mirrors, similarly named projects, stale downloads, or unrelated products on the same company domain before making a link primary. An official outbound link is a separate fact from whether we recommend the app.
Unknown
Unknown does not mean No
Unknown means we do not currently have enough reliable evidence to make a bounded claim. It does not mean unsupported, closed source, unsafe, or unavailable unless the evidence actually supports that conclusion.
Freshness
Current beats announced
Roadmap announcements do not become current facts until the feature ships in the relevant release context. Stable, beta, preview, and planned support can be recorded separately. Material facts are re-checked on different cadences and may be marked as needing re-verification when evidence gets stale.
Corrections
See something wrong or outdated?
Send the official source or other strong evidence through the app submission path. We review factual corrections independently from editorial recommendations, and submitting evidence does not guarantee a badge or editorial conclusion.