PUBLIC.2 SAVED-EVIDENCE INSPECTION — NO LIVE EXECUTION

1. Obtain trusted expected ZIP and manifest digests independently. Check ZIP hash
before extraction. The offline verifier reads the archive without extraction.
SHA256SUMS beside an unsigned download is not an authenticated trust root.
2. Review tools/verify_public_edition.py, then run with a local Python 3 standard
library (no installation): python3 -I -B verify_public_edition.py /path/to/public.2.zip
--expected-archive <trusted ZIP SHA256> --expected-manifest <trusted manifest SHA256>.
Use one command line. The publication folder supplies a ready verification command.
3. Optional private derivation check: add --source-public-one /path/to/public.1.zip.
This compares source and projection identities using the pinned immutable public.1.
Original Release 220 and its signed manifest remain required for independent full
original-container ancestry verification. The public subset alone cannot do that.
4. Inspect the five cases, 22 ledger rows, receipts/events, authority before/after,
native journal MESSAGE replies and numeric UID/GID 5200/5206. Original substantive
bytes remain exact; identity-bearing wrappers are explicitly projected. Synthetic
opaque labels preserve equality/record uniqueness without publishing raw identity.
Whole projected files no longer possess original byte authentication. No redaction
attestation has been signed. New manifest signing is a separate owner step after
independent acceptance; signing authenticates bytes, not historical truth.
5. Public.2 omits the full current maintenance capture, replay result, execution
wrapper and pure maintenance verifier. It cannot reproduce complete maintenance
replay, contiguous full-journal checks, host/boot binding or maintenance health.
Prior maintenance PASS statements in preserved historical reports are historical
claims only. Native process/ledger/physical evidence remains inspectable, but does
not replace the omitted maintenance proof. No new maintenance verdict is asserted.
6. No runtime, native dependency distributions, full installer, earlier maintenance
history, complete 170-source/3658-installation-entry replay or experiment rerun is
supplied. Dependency acquisition identities remain references, not availability or
current-license guarantees. Manual target code/errno/results remain absent, scope
was confounded by replay, and live same-tick mutation was not executed.
7. HISTORICAL-REFERENCE-STATUS.json maps retained historical references to exact
bytes, privacy projections or unavailable original sources. Old manifests and
source procedures describe larger releases and cannot validate public.2 as those
releases. Fixture results are not live evidence. Do not run historical commands,
projected observer source, installers or attacks during evidence inspection.

Retrieval, reading and learning confer no execution authority. The trusted host,
kernel and capture mechanism remain assumptions; hashes do not witness history.
