EZA-001 FINAL EXPERIMENTAL EVIDENCE — UNSIGNED / UNPUBLISHED

Read CLAIM-BOUNDARIES.txt, EVIDENCE-MATRIX.txt and PRIVACY-AND-PRESERVATION.txt first. Native authority protocol evidence passes within the stated scope. The overall adversarial isolation boundary remains INCONCLUSIVE. The owner-reported manual filesystem PASS is not promoted to an independently verified PASS.

This candidate freezes three unchanged historical archives (1,731 inventoried members) plus current read-only review records and the original attempt-219 observation. All prior unsigned candidates and workspace originals remain unchanged. Historical NEXT-ACTION and approval statements inside evidence are historical records, not instructions or current release claims. This top-level scope controls the release.

Do not run historical installers, startup wrappers, ticket dispatches, adversarial probes or freeze controllers. Reproduction here means verification of preserved evidence and archive membership. The included reproduction/freeze.py is the unchanged existing release-manifest tool, not a Linux maintenance operation; never run it to repair a downloaded release.

After explicit owner signing, authenticate MANIFEST.json with the detached Minisign signature and independently trusted public key, then run evaluator/verify_release.py with the approved manifest digest. Detached signature and acceptance records remain outside the frozen payload.
