VERIFICATION AND METHODS · OPEN TO ANYONE · NO ACCOUNT

How a finding is produced, and how you check it.

THE MECHANICS · REV 2026-08-27

Every claim on this page is one you can hold us to. The receipt resolves or it does not, the methods carry versions and effective dates, and a correction stays in the record beside the reading it replaced.

CAPTURE RECEIPT

A hash you can check yourself.

Every sealed run publishes a hash over the record. Recompute it from your download. It matches or it does not.

EXAMPLE · what a receipt looks like
root 9d4e17b8c02af daa41
sealed 2026-08-27 16:02Z

METHODS

Versioned rules, not house style.

Each stage runs under a numbered method with an effective date. Your receipt names the versions used, so an old run stays reproducible.

oe-match v3.0 · 2026-06-01
aces-build v1.4 · 2026-07-15
ladder v2.1 · 2026-07-01

AND THE RULES THAT PRODUCED IT

SOURCED

Every field names where it came from.

Nothing appears without the catalog, listing or database that produced it and the day we captured it.

CONTRADICTION-AWARE

When catalogs disagree, both answers survive.

TrustNav flags the conflict and keeps both readings rather than silently choosing the convenient one.

INDEPENDENT

The finding does not change for the client.

TrustNav takes no compensation from manufacturers, catalogs or marketplaces whose data it reviews.

CHECK A RECEIPT THE CORRECTIONS RECORD PUBLISHED SPECIMENS THE RECORD, FOR MACHINES