# Verifier notes

## Run

`python3 code/check_vectors.py` ran in rootless podman with no network, on an image built from `env/requirements.txt` (`cryptography==50.0.2`) on `docker.io/library/python:3.12-slim`. Exit code 0 after 0.70 s, within the 1.5-minute limit.

All six files under `results/` that the run wrote are byte-for-byte equal to the declared files in the bundle: R1 through R6, including fields the claim table does not name. All 14 declared results therefore agree (tolerance 0). Verdicts C1–C6: reproduced.

## Hidden content

The four findings in `scan.json` are labeled test-vector cases, not instructions aimed at a verifier:

- `data/bundle-vectors.json` line 63 (`U+007F`) is the path `code/run` + DEL + `.py` in a case named "the DEL character".
- `data/bundle-vectors.json` lines 133 and 139 (`U+E000`) are a synthetic path `data/` + U+E000 + `.txt` in a case named "paths whose UTF-16 order differs from their code-point order".
- `data/claim-id-vectors.json` line 98 (`U+FDD0`) is the string "Broken " + U+FDD0 + " text." in a case named "a Unicode noncharacter in a string".

No other control, private-use, noncharacter, or bidi-override characters were found in the bundle text files.

## Hazard screen

none. The work is protocol conformance vectors and a checker. The signature vectors include keys the paper says are for these vectors only. The unusual characters above are inputs to those tests.
