Methodology

How XRCompat decides compatibility

Facts first, rules second, pages last. We separate device facts, connection rules, evidence claims and commercial offers so a monetization decision cannot change a compatibility result.

01

Official facts

Host video output, glasses input protocols, power requirements and accessory capabilities are stored as atomic facts with source records and verification dates.

02

Connection inference

A rules engine searches direct and adapter routes. Exact manufacturer confirmation is labeled High / Manufacturer verified; a route inferred from A-grade official specifications stays Medium / Protocol-derived.

03

Conflict handling

Conflicting claims are not silently resolved. Affected pairs are downgraded, marked for review and held from the launch index when necessary.

04

Index Governor

Not every database combination becomes an SEO page. Unknown or conflicted pairs remain accessible for research but are kept out of the sitemap and receive noindex.

Evidence labels

What the labels mean

Manufacturer verifiedHigh confidenceThe manufacturer explicitly names the pair or connection route.
Protocol-derivedMedium confidenceOfficial specifications on both sides support the route, but the exact pair is not explicitly named.
Evidence conflictReview requiredAuthoritative sources disagree; the conflict is exposed rather than hidden.