The Verify Standard, v1
A claim is verifiable when a stranger can rerun it. This page is an open standard for that sentence, distilled from the harness that seals every AssetShop release, offered to the whole market including our competitors, because a category is owned by whoever publishes its yardstick.
The five requirements
One, a receipt: a content hash over the shipped tree, re-derivable with no vendor credentials. Two, a battery: assertions whose total is computed, never typed, with per-suite figures the independent run reconciles exactly. Three, labels as law: MODELED and SYNTHETIC enforced by tests that fail on an unlabeled figure. Four, claim-runtime pairing: every public claim names the runtime that proves it or carries a status label. Five, one command: the whole verification runs cold, and refusals answer politely with their reason.
The one line for buyers
Ask your vendor for the command.
If they have one, run it on day one and read what it names. If they do not, you have learned the most important thing a diligence process can teach. Ours is ./verify at every release root, and the last cold run by a stranger machine returned twenty-eight checks of twenty-eight.
License
Published openly; adopt it, adapt it, hold us to it. The reference implementation ships inside every AssetShop release as DILIGENCE.sh with a supplied-log contract for locked-down environments.
You do not have to take our word for anything: every claim on this estate is independently verifiable, and the harness that proves it ships with the product. Every figure on this page is computed at build or wears its label.