SOURCE TRANSPARENCY
A source being enabled means it is approved for research under the recorded scope. It does not make every claim from that source automatically correct; each model, region, date and calculation still needs review.
Pixel OS and security-support commitments
Cadence: weekly · Storage: Structured claims and short evidence snapshot · Link and factual extraction approved; no page reproductionOpen official source ↗Current monthly, quarterly and biannual security-update scope
Cadence: weekly · Storage: Structured scope changes and short evidence snapshot · Link and factual extraction approved; no bulletin reproductionOpen official source ↗Candidate generation and official recall notices
Cadence: daily · Storage: Normalized notice facts, identifiers, hash and official link · US government source; attribution and source link retainedOpen official source ↗Candidate generation for non-food product safety alerts
Cadence: daily · Storage: Disabled until parser, terms and matching fixtures pass · Pending source-specific ingestion reviewOpen official source ↗Future vulnerability context, never automatic device impact
Cadence: daily · Storage: Disabled; no device mappings stored · Pending matching and false-positive safeguardsOpen official source ↗Future comparable repairability and battery attributes
Cadence: monthly · Storage: Disabled until scheme/version fields and fixtures pass · Pending source-specific terms and reuse reviewOpen official source ↗Derived claims must identify the source, checked date, jurisdiction and relationship to the displayed fact. Policy calculations also record the start event, duration, rounding rule and date precision. Stale or conflicting evidence returns to editorial review.