Editorial method · version 1.0

A support state is
a scoped claim.

Feature State records what a particular product surface supports under stated conditions. We do not convert model capability, marketing language, or missing evidence into a universal answer.

Unit of research

The atomic record is a relationship between one product and one defined capability. A record can additionally name a model, plan, platform, region, or rollout condition. Product records are not inferred from model API documentation unless that documentation explicitly applies to the product surface.

product×capability×conditions+dated evidence

Support states

“Supported” is reserved for clear primary evidence without a material plan or platform limitation. Conditional, selected-plan, selected-platform, partial, and experimental states keep those qualifications visible.

Supported
Primary evidence establishes the capability on the reviewed product surface.
Partial
Only a meaningful subset of the capability definition is supported.
Conditional
Support depends on setup, integration, approval, or another stated condition.
Selected plans
The capability is limited to named subscription or organization plans.
Selected platforms
The capability is limited to named operating systems, interfaces, or surfaces.
Experimental
The vendor labels the feature preview, beta, experimental, or similarly provisional.
Unknown
The research pass did not find enough primary evidence. This is not a negative claim.

Source hierarchy

  1. Official product and API documentation
  2. Official announcements, release notes, support pages, and repositories
  3. Regulatory or institutional documents
  4. Reproducible independent testing
  5. Reliable journalism and specialist technical publications
  6. Community reports, used only as provisional leads

Search snippets, AI summaries, affiliate comparisons, and anonymous posts are not treated as evidence. See the full source policy.

Confidence

High confidence means direct and current primary evidence closely matches the claim. Medium confidence indicates ambiguity in scope, product naming, or rollout. Low confidence is used for unresolved evidence and generally results in an unknown state.

Change protocol

When a verified state changes, the previous state remains in the public change log with the date, new state, source, and a concise explanation. Announcements are not treated as confirmed availability unless the source establishes that users can access the feature.

Automation and human review

Automated tools assist with source discovery, data validation, stale record detection, page generation, and link checks. They do not publish factual changes automatically. Every classified record in this release was assembled from primary evidence and requires human review before a production update.

Feature State is independent and does not accept payment for a support state. Vendors may submit evidence through the same correction process available to everyone.