Independent pre-launch previewNo live vehicle lookupNo affiliate tracking
CarIntegrityBuild a check plan

Methodology / Version 1.0

Evidence first. Automation second.

CarIntegrity is designed to be AI-operated without treating AI as evidence. Source rights, deterministic code, independent gates, and visible limitations come before page count or affiliate revenue.

The operating rule

Model text is not evidence.

A publishable fact must trace to a retained source artifact, deterministic calculation, executable test, or signed tool receipt. AI output can improve explanation and workflow speed; it cannot substitute for provenance.

The publication pipeline

Six controlled stages

A failure at any stage blocks or quarantines the affected source, page, or release.

  1. 01

    Admit the source

    Record ownership, jurisdiction, licence, attribution, storage rights, fields, update cadence, privacy risk, and correction process. Unknown rights block use.

  2. 02

    Archive the evidence

    Retain the raw source artifact with a checksum and retrieval time. A webpage or model summary alone is not evidence.

  3. 03

    Parse deterministically

    Typed, versioned code owns identifiers, dates, calculations, routing, and quality checks. Missing, zero, withheld, and unknown stay distinct.

  4. 04

    Draft from a fact packet

    AI may explain approved evidence. It cannot invent facts, reviewers, experience, quotes, or a relationship with a provider.

  5. 05

    Gate the page

    Code checks sources, freshness, uniqueness, canonical, locale, rendered HTML, structured data, accessibility, and performance before indexation.

  6. 06

    Observe and correct

    Sources and pages are monitored. Ambiguous data is quarantined, last known good data is retained, and substantive corrections remain visible.

What AI may do

Research, structure, draft, and monitor.

  • Discover candidate official or licensed sources.
  • Prepare a source dossier for rights review.
  • Draft explanations from an approved fact packet.
  • Translate an already approved source-language artifact.
  • Watch for source, schema, freshness, and page changes.

What AI may not do

Invent authority or bypass a gate.

  • Act as the factual source.
  • Claim a human author, reviewer, test, or experience.
  • Accept source or affiliate terms for the owner.
  • Publish allegations or personally identifying data.
  • Force a thin page into the index.

Page policy

Indexation is earned page by page.

A generated URL is not automatically a publishable page. Before indexation, every page family must demonstrate page-specific utility, correct locale and canonical signals, source visibility, required freshness and sample size, server-rendered primary content, crawlable links, valid matching structured data, accessibility, performance, and duplicate-content safety.

GatePass evidenceFailure action
SourcesOwner, date, coverage, rights, checksumBlock or quarantine
Unique utilityData, analysis, or useful toolKeep unpublished
Technical SEORendered policy test suiteNoindex and remove from sitemap
ReleaseMaker, verifier, artifact digest, canaryStop or roll back

Commercial independence

Money may place an offer. It may not change the facts.

Affiliate relationships are disclosed before the first commercial call to action. Links use the sponsored qualification. Provider order or scoring must follow a published, reproducible method—not commission.

Read the affiliate policy

Corrections

Correct the record without erasing the trail.

A correction records the affected claim, former value, new evidence, change date, and responsible run. Source outages keep last known good data visible with a freshness warning rather than silently replacing it with zero.

External standards

Technical references for this preview

Source
Google Search Central, web.dev, and W3C
Observed
28 Jul 2026
Coverage
Technical policy and target selection for this English preview
Limitation
Search eligibility never guarantees ranking or indexation

Methodology reviewed 28 July 2026.