DevLifeCheck

METHODOLOGY

Every claim needs evidence

DevLifeCheck separates facts, calculations and estimates so a confident-looking interface never hides uncertainty.

Evidence hierarchy

AOfficial confirmedManufacturer policy, product page, regulator or recall authority
BPolicy-derivedCalculated from an official duration and documented start date
CCorroboratedMultiple reliable secondary sources agree
DEstimatedReasoned estimate with limitations stated
UUnknownNo defensible date is publicly available

Review workflow

  1. DiscoverFind a manufacturer, regulator or other permitted source.
  2. ParseCapture the exact claim, region, model family and effective date.
  3. MatchResolve variants and avoid transferring a claim to an unsupported model.
  4. VerifyA reviewer checks the source and calculation independently.
  5. PublishThe record receives a confidence label and review date.
  6. MonitorPolicy changes and stale evidence return to the review queue.

Wording rules

We do not say a device “is secure.” We say it is within a stated security-support period. We do not say “no recalls exist.” We say no matching notices were found in the sources checked on a specific date.