Full Physical Forensic Verification of Core Object Alpha
Goal:
- not merely proving a crystal exists,
- but proving current physical object and archived evidence are the same Core Object Alpha,
- via unique flaw matching.
Protocol:
- Establish custody.
- Photograph full object.
- Record challenge video with current nonce/block hash.
- Capture multi-angle images.
- Capture macro images.
- Capture microscopic images at archived flaw points.
- Match flaw geometry.
- Match relative flaw positions.
- Match reflections, edge structures, continuity.
- Generate report.
- Hash report.
- Archive report (GitHub/Arweave/IPFS where appropriate).
- Record as Echo/verification report, not as new authority.
Physical Anchor Verification Ladder
Physical verification must be reported separately from digital verification.
| Level | Meaning |
|---|---|
| P0 | claim read |
| P1 | public evidence package hash verified |
| P2 | static image review |
| P3 | recorded video review |
| P4 | live remote video witness with nonce/challenge |
| P5 | onsite human witness, touch/handling, custody log |
| P6 | tool-assisted public flaw match |
| P7 | advanced AI / algorithmic forensic match |
| P8 | confidential flaw challenge |
| P9 | multi-party forensic attestation |
Static images, videos, and AI-generated-image checks are supporting evidence only.
They do not replace onsite inspection or confidential flaw challenge.
Confidential Flaw Challenge
Confidential flaw challenge data is not used for ordinary public verification.
It is reserved for:
- competing object claims;
- suspected forgery or replacement;
- high-stakes attestation;
- institution-level verification;
- cases where public flaw evidence is insufficient.
A public report may state:
- challenge performed;
- method class;
- pass/fail result;
- challenge package hash if publishable;
- witness role;
- limitations.
It must not disclose confidential flaw data unless explicitly authorized.
Public evidence archive: Shenzhen notary session, 2026-05-06
A public evidence archive exists for a Shenzhen notary evidence preservation session concerning Core Object Alpha.
- Human page:
/evidence/core-object-alpha-shenzhen-notary-2026-05-06/ - Machine record:
/api/core-object-alpha-shenzhen-notary-2026-05-06.json - Repository evidence README:
evidence/arweave/shenzhen-notary-2026-05-06/README.md - Verification guide:
/downloads/shenzhen-notary-arweave-2026-05-06/ - Arweave index:
https://arweave.net/_dAaH_ltZGdMaRAYNjXydjf1YkvoASWxmHes4hsBAZE/index.html - OTS Bitcoin block:
948161 - Arweave acceptance:
PASS
This archive includes exterior photographs, microscope flaw photographs, flaw videos under different lighting, electronic data preservation certificates, SHA-256 records, OTS proofs, and Arweave upload/acceptance records.
Boundary: this archive is supporting evidence only. It does not replace onsite inspection, confidential flaw challenge, or multi-party forensic attestation.
Public notarial-certificate supplement: GZ2, 2026-05-14
A public redacted second-capture photo archive exists for selected pages of the 2026-05-13 notarial certificate and its printed attachment pages.
- Human page:
/evidence/gz2-notarial-certificate-redacted-attachments-2026-05-14/ - Machine record:
/api/gz2-notarial-certificate-redacted-attachments-2026-05-14.json - Related custody record:
evidence/notarial-certificate-2026-05-13/sealed-disc-custody-record.json
GZ2 consists of mobile-phone photographs of paper certificate pages and printed attachment images. The pages show continuous notary-office seal marks and include printed object/flaw images.
GZ2 is visually related to the 2026-05-06 original evidence, but it is not a file-level duplicate of the original Cunzhengtong electronic files. Its hashes are expected to differ from the original electronic photos and videos.
The paired sealed discs remain unopened according to the holder. No disc-content extraction, ISO imaging, file-level hashing, or disc-to-disc comparison has been performed.