# Verifying the public evidence pack

Requirements: Python 3.10 or newer.

Download [the complete public evidence pack](downloads/DRENDA_PUBLIC_EVIDENCE_PACK.zip)
and its [SHA-256 checksum](downloads/DRENDA_PUBLIC_EVIDENCE_PACK.zip.sha256).
Compare the archive digest before extracting it. The same-site checksum detects
transfer changes; it does not establish independent authenticity.

The ZIP has exactly nine files: five EVIDENCE JSON records, `manifest.json`,
`claim-registry.json`, `VERIFY_EVIDENCE.py` and these instructions. It contains
only already-public records and no Resident, runtime state or private holdout.
Alternatively, download those files individually from the evidence index.

From this directory run:

```text
python VERIFY_EVIDENCE.py
```

Expected result:

```text
DRENDA_PUBLIC_EVIDENCE_PACK: PASS
```

The verifier checks file membership, SHA-256 hashes, JSON parseability, evidence IDs, and privacy markers. A PASS establishes package integrity only. It does not validate the truth of the underlying scientific claim.

More precisely, it checks the five files listed in `manifest.json`; it does
not authenticate the claim registry or itself, and does not reject extra
files in the directory. The published ZIP checksum covers the full archive.
A `SANITIZED` marker is a label, not proof that an arbitrary file is safe.

For a signed challenge ZIP, use the separate
[Level 2 proof guide](../verify/#signed-proof). To produce your own new proof,
follow [the new-challenge steps](../eval/#new-challenge). Neither verifier
reruns D0/D1/D2 or the private Resident. The signed-proof verifier checks the
specific registered T01/T02/T03 contract; the evidence-pack checker only checks
the five descriptive records. T03 covers bounded learning and same-grammar
reuse, not transfer to a different problem family.