Evidence before opinion.
How COMPUTER USE verifies claims, qualifies pages and separates commercial interests.
Primary sources
Official documentation, pricing, repositories and original benchmark methods are the evidence base.
Visible uncertainty
Unknown, partial and not applicable are separate states. Silence is not evidence of absence.
Independent judgment
Payment cannot change facts, benchmark scores, verdicts or alphabetical editorial order.
What “verified” means
We opened the primary source on the recorded retrieval date and checked the publisher’s stated fact. This is documentary verification. We have not independently reproduced each vendor’s capability, security guarantee or benchmark. Editorial workflow recommendations are interpretations, and are labeled as such.
There is no universal product score. Directory ordering is alphabetical. Benchmark records preserve their release, harness, date and source type; incompatible scores are never blended.
Freshness windows
| FACT TYPE | REVIEW WINDOW | WHEN IT EXPIRES |
|---|---|---|
| Pricing | 14 days | Current amounts and calculator inputs are suppressed |
| Model / API capabilities | 30 days | Review due badge; original date remains visible |
| Product capabilities | 45 days | Review due badge |
| Security / compliance | 90 days | Recheck primary trust/security evidence |
| Company background | 180 days | Recheck original company source |
| Versioned benchmark | Historical record | Do not relabel as a current model; review URL health quarterly |
Publication gates
- Profiles require at least five evidenced capabilities, three distinct primary source URLs, a verified status, stack position, limitations and a verification date.
- Comparisons require qualified profiles, at least six displayed dimensions, four substantive differences or complementarities, six combined primary sources and workflow-specific decisions.
- Alternatives require at least five sourced options, disclosed selection criteria, and an explicit substitute/complement distinction.
- Use cases must explain the task, API-first decision, architecture options, risks and approval point. Workflows add prerequisites, steps, costs and recovery guidance.
- Failed candidates stay noindex or withheld. A planned route is never counted as authored content.
Research limitations
Public documentation may omit behavior, contradict older pages, or change after retrieval. An evidence record reflects its source, not an assurance that a tool will work in your environment. Benchmark results shown here are externally reported; COMPUTER USE did not run them.
Our data is maintained in version-controlled records. A source correction updates dependent profiles, comparisons and calculators together. Inspect the evidence ledger and research log.