DERIVED PRIVACY PROJECTION — NOT BYTE-IDENTICAL TO HISTORICAL SOURCE
Source public.1 SHA256: b8a391de97fe1fe675cce1a5ee3bb2fa050ec7295366c914f5eaa0f23332e220
PUBLIC2-OPAQUE labels are synthetic; original signature does not cover these bytes.
Historical assessments below retain their historical scope, subject to public.2 limitations.

EZA-001 — RUNTIME INPUT ACQUISITION 106
COMPLETE — acquired and verified; STOPPED for owner manifest approval.
READY as a source/wheel input bundle for private CPython 3.12.14 compilation.
This is not a runtime build, promotion, installed-runtime verification or custody
startup result. No build is authorized by this report.

TARGET AND TOOL INTEGRITY
VM 002 identity confirmed: PUBLIC2-OPAQUE-GUEST-01, ARM64,
PUBLIC2-OPAQUE-MACHINE-01, boot 32e42e30-505b-4cce-bb5f-0190a9da2fc6.
Correction 101 checksum-file digest and every listed source/pin file verified.
The existing 049 fetch_runtime_inputs.py ran unchanged with exactly the same
nine-version requirements-pins.txt. Acquisition exit code 0. Inputs are retained
on the host only in this directory's inputs/; no guest staging occurred.

AUTHENTICATION
CPython source SHA256 equals the pre-established Correction 101 pin AND the
independently retrieved exact XZ source row on the official Python.org release
page over default certificate/hostname-verified HTTPS. Source patchlevel.h says
3.12.14; all archive members satisfy the existing builder's safe-member rule.
Each wheel SHA256/size matches the original PyPI release JSON. Every selected
wheel's exact filename, hash, URL and non-yanked status also matches a separately
retrieved official PyPI Simple API response over verified HTTPS. Original
metadata and authentication response bytes/headers/digests are preserved.
This authenticates against established upstream repository identities and the
existing source pin. GPG/Sigstore publisher signatures were not verified and
are not claimed; HTTPS/hash checks do not prove absence of malicious source.

CONTENT / COMPATIBILITY
Exactly one source archive, nine wheels, nine original release metadata JSON
files, requirements.lock and the original runtime-inputs.json are retained.
No missing, extra, conflicting or substituted input. Manifest/lock agree with
all actual file hashes; nine package names and versions are exact.
All wheel RECORD membership, hashes and sizes verified; unsafe paths, symlinks,
.pth and customization files rejected. Filename and internal WHEEL tags agree.
Six wheels are py3-none-any; cffi and rpds-py are cp312-cp312 ARM64; cryptography
is cp311-abi3 ARM64, compatible with CPython 3.12. All native wheel files are
ELF64 little-endian AArch64; manylinux tags require glibc 2.17, compatible with
VM 002's recorded Ubuntu glibc 2.39. Requires-Python and every active non-extra
Requires-Dist evaluated for Linux AArch64 CPython 3.12.14; closure is satisfied
by the exact nine approved versions. No missing/unsupported dependency.
No source, extension module or wheel code was run to obtain these results.

REVIEW ARTIFACTS
inputs/runtime-inputs.json: unchanged hash-only manifest consumed by existing
build_runtime.py. This is the INPUTS_SHA for explicit owner review:
75165d0da01c5e50ebd9d9fbb43328a42cb7886afe99e2ffd592259e07924165
INPUTS-MANIFEST-WITH-SIZES.json: supplemental complete 21-file inventory,
including the build manifest, with exact byte counts and SHA256 identities.
Supplemental inventory SHA256 (NOT build_runtime.py's INPUTS_SHA):
2d2e4f70c1a5e42763f2495777e33e986d45df5a8f3243cd5bbdcfb78722a2ff
INPUTS.tsv: concise complete inventory of the same 21 files.
verification.json: per-wheel metadata, active dependency decisions, tags, native
file identities, RECORD verification and authentication reference records.
authentication-references/: original upstream response bodies; gzip-decoded
HTML is retained separately. reference-retrieval.json records transport facts.
source-integrity.json and preservation.json: unchanged tool/prior-evidence checks.

VERIFICATION PROCESS OBSERVATIONS
Two preliminary local parser attempts encountered HTTP gzip encoding and an
HTML checksum split by display markup. Both attempts are preserved. The verifier
was corrected to decode gzip and read the exact source table row; the original
response was reused and its retained hash rechecked. No trusted digest, source
pin, acquisition helper or input bytes were changed. The complete third pass
succeeded. This was verification-parser correction, not an acquisition retry.

LIMITS / NEXT OWNER DECISION
Approve the exact build input manifest digest above before any build. Runtime
compilation, module execution, sys.base_prefix and unchanged custody runtime
checks remain untested. The approved tools/inputs still require controlled guest
staging and genuine package-evidence capture/review under the existing Correction
101 procedure; the current task performs acquisition and verification only.
No wheel installation, Python compilation, /opt promotion, custody changes,
old-installer replay, other VM access, signing, publication or deployment occurred.
