Verification and Reproducibility

Reproducibility requires more than running the same button twice. Knotest records content identities for Project inputs, the compiled Evaluation, stage outputs, runtime provenance, Claims, and Evidence.

What Verification decides

Verification independently checks that Project owners, Materials, a Claim's compiled plan, Stage Claims, Evidence, and completion policy agree with their recorded identities.

It does not:

• treat successful worker output as sufficient proof;
• silently accept changed Model or Dataset bytes;
• repair a Claim or Evidence file;
• replace missing Evidence with a new calculation; or
• turn an incomplete Evaluation into a completed one.

Reuse without mutation

A sealed Prediction Set can support multiple compatible Evaluations. A retained Claim and its Evidence remain immutable. New assumptions, thresholds, inputs, or coverage produce a new record rather than rewriting history.

This is why the evaluation record is the product: another reader can inspect what was assessed, which exact inputs and settings were used, what completed, and whether the retained files still verify.