Editorial information

How we verify

We prefer incomplete, traceable records over complete-looking claims assembled from memory or secondary listings.

Source hierarchy

Device specifications come from manufacturer product, support, or developer documentation. Standards come from the organization maintaining the specification, including registries and formal specification pages. Technical concepts use standards, public technical documentation, and scientific or institutional sources. Application claims require a documented primary source and are not generalized beyond what that source establishes.

Record process

An editor identifies the exact item, captures the primary URL, checks each structured field, records the verification date, and leaves unsupported values unresolved. A page is not evidence that a device was physically tested. We do not convert retailer copy, search snippets, or community database entries into manufacturer facts.

Corrections and aging

Hardware records display a data-as-of date because documentation and support status change. Readers should re-open the primary source before procurement. Corrections can be sent through the contact page with the affected URL, disputed field, and a primary source that supports the change.