Schemas and standalone verifiers for the lab's evidence

Counted in one directory of the lab's code at a named commit

Schema files: 14
Of them, forbidding undeclared fields: 14
Standalone verifier programs: 11

A verifier does not import the program that wrote the file; paired verifiers share their checks.

The result

Several of the lab's evidence formats have a strict schema and a standalone verifier whose exit code is the verdict and which does not import the program that wrote the file; paired verifiers share their checks, so they are not independent implementations

What it does not claim

It counts files and reads schema settings; it does not run the verifiers here. Import independence is not implementation independence: both verifiers of a pair apply the same checks, and every escalated forgery the lab recorded got past both until someone attacked them. The lab's code is not public yet.

The limits, in the lab’s words:

NEG-F5-07 applies directly — 'two independent verifiers' is IMPORT-independent, not IMPLEMENTATION-independent: same checks, same report order, SAME OMISSIONS, and every forgery escalation survived in both until someone attacked.

Excerpts, word for word from the published file, where the full text can be read.

A result is only as good as the check that reads its evidence. The lab writes each kind of evidence file to a JSON schema that forbids fields it does not declare, and checks it with a small verifier program whose exit code is its verdict. A verifier does not import the program that produced the file, so a bug in the producer is not inherited by the import.

What it shows

In this count: the files in one directory of the lab's code at a named commit, counted by this site's own script.

The directory holds 14 schema files, and 14 of them forbid any field they do not declare and require at least one. It holds 11 verifier programs. The lab's own record had claimed a different number of each, and its limits state the counted ones; the count here agrees with them.

Why it matters, and to whom

For a buyer checking the lab's results, a verifier that does not share code with the producer can be read and run on its own, against a file the producer wrote. It narrows what has to be trusted. It does not remove it: the two verifiers of a pair were written from the same list of checks, so they miss the same things.

Why now

Results in this field are increasingly published as files a reader is asked to trust. A strict schema and a standalone checker make each such file checkable by its exit code, the way the verifier on this site's home page checks a file's fingerprint in the browser.

How it was checked

This site's script listed the directory at the lab commit, counted schema files and verifier files by name, and read each schema to see whether it forbids undeclared fields and requires at least one. The file names are committed by the hash of their sorted list.

How to reproduce

The count names the lab commit and directory. Anyone with access to the lab's code can list the same directory and recount. The claim and limits are copied word for word. Each file is listed with its hash in the site's receipt manifest.

The result, in the lab’s exact words

Read it with this condition: "does not import the producer" is the whole of the independence claimed. Two verifiers for the same file share their checks and their omissions, so a forgery that passes one passed both until it was found.

A reusable artifact-verification substrate where the exit code is the verdict and the verifier does not import the producer.

Quoted word for word from the lab’s published claim and limits.

Prior art

JSON Schema specification: the schema language the lab's evidence formats are written in

Evidence

The measured results behind this page, read from the lab’s own files at a named version.
The lab’s current claim and limits, word for word.
Every file this site publishes.