Source Policy
A simple evidence hierarchy for a topic where documentation can change within hours.
Source hierarchy
| Priority | Source type | Used for |
|---|---|---|
| 1 | Official model/API documentation | Specs, pricing, endpoints, tools, limits |
| 2 | Official launch posts and changelogs | Release details, rollout, product changes |
| 3 | Official partner documentation | Platform-specific availability and integrations |
| 4 | Reputable independent testing | Performance context and external validation |
| 5 | News and community sources | Discovery and context only when better evidence is unavailable |
Conflict handling
If two official pages disagree, we prefer the page that is most specific to the claim and clearly state the ambiguity when it can change a reader’s decision. A model-specific pricing table, for example, is treated separately from unrelated enterprise metering documentation.
Linking standard
Important factual pages include a Sources section linking directly to the underlying documentation. We avoid citing search-result snippets when a stable primary page is available.
Freshness
High-volatility facts such as pricing, availability and API capabilities are reviewed more frequently than background explanations. A new review date means the factual content was checked, not merely that the page timestamp was refreshed.