A model fact should be traceable to the document that supports it.
DeviceOK stores the source, verification date and diagnostic boundary with version-sensitive records. A page should not become more confident than the evidence behind it.
What gets trusted first
Model specifications, ports, charging behavior, official errors, permissions, drivers, firmware, repair and native diagnostics.
USB, Bluetooth, W3C web APIs and other protocol behavior where the specification is the authoritative boundary.
Used when a primary source describes the mechanism but not the practical symptom, or when independent implementation notes clarify a browser/device behavior.
Useful for finding a reproducible pattern. Not enough by themselves for a risky repair instruction, exact model specification or compatibility claim.
How a factual record is reviewed
“Does this laptop have USB-C?” is different from “Does this USB-C port support charging?” and different again from “Does it output DisplayPort video?” Each requires its own evidence.
Names can be reused across hardware revisions. DeviceOK avoids turning one regional specification or generation into a universal claim.
Requirements, caveats, verification steps and the browser/native boundary are stored beside the answer so search snippets do not erase the conditions.
A published model, test, compatibility answer or diagnostic path must point to real internal records. The build audit rejects stale model→test and compatibility→model references.
A database record can power internal search without becoming a Google page. Indexable factual records need a distinct intent, provenance, a verification date and enough unique value to resolve the query.
“Last verified” is not decorative
It means the cited source and the DeviceOK interpretation were checked on that date. App/browser/OS guidance should be reviewed more frequently than stable concepts such as connector dimensions or long-lived web standards.
A sitemap modification date is changed for meaningful content or source updates—not merely because the application was redeployed.
When sources disagree
DeviceOK narrows the claim to the model, revision, region or software version both sources can support. A newer official specification can supersede older documentation; if the conflict cannot be resolved, the page should show the uncertainty instead of selecting the more convenient answer.
Retail listings and generated compatibility tables do not override the device maker or applicable standard.