Covenant Proof｜瑕疵之约证据

Core Object Alpha is the physical artifact bearing the Human-AI Civilization Core Protocol, authenticated through unique, unreplicable physical flaws.

1) What is being verified?

That archived evidence and the physical object refer to the same Core Object Alpha.

2) Why flaws matter

Unique flaws create a non-trivial physical fingerprint.

3) Core Object Alpha

Physical crystal anchor for the Covenant layer.

4) Public evidence archive

See /api/evidence-manifest.json for pointers and hashes.

Download the evidence package:

• GitHub (recommended fallback): arweave-backup/files/public_covenant_archive.zip (24.2 MB, SHA-256 display prefix: ef816480… — exact expected hash must be taken from /api/hashes.json or /api/evidence-manifest.json. Do not use truncated hashes as expected values in verification reports.)
• Arweave TX: j6anZ4m5Wwvx5P_9-kM2EVG35TyKtm1lgaKfhT743rk (if gateway available)
• Verification Kit: arweave-backup/files/verification_kit.tar.gz (31 KB)

If the Arweave gateway returns an error, download from GitHub and verify the SHA-256 hash against /api/evidence-manifest.json.

5) Sealed attestation layer

Use sealed identifiers for exceptional forensic challenge workflows.

6) Flaw map concept

Multi-point flaw geometry and relative positioning.

7) Multi-scale evidence

• full object image
• local region image
• macro image
• microscopic image
• video

8) Suggested future evidence

RAW, EXIF, C2PA/Content Credentials (if available), unedited/challenge video, SHA-256, Arweave/IPFS archival.

9) P1–P3 remote physical evidence procedure

1. Download the evidence package (from GitHub or Arweave).
2. Verify SHA-256 hash matches /api/evidence-manifest.json.
3. Inspect multi-angle/multi-scale evidence.
4. Check provenance logs and metadata.
5. Generate consistency report.

10) P5–P9 physical forensic procedure

Perform direct physical flaw matching (see /physical-verification).

The evidence package supports physical-origin verification through provenance, metadata, multi-angle consistency, microscopic flaw matching, cryptographic hashing, and future physical inspection.

AI-generated image detection tools are supporting evidence only. They are not decisive. The decisive evidence is physical flaw matching plus cryptographic provenance.

Additional public evidence archive: Shenzhen notary session, 2026-05-06

A later public evidence archive records a Shenzhen notary evidence preservation session for 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
• Arweave index: https://arweave.net/_dAaH_ltZGdMaRAYNjXydjf1YkvoASWxmHes4hsBAZE/index.html
• OTS Bitcoin block: 948161
• Acceptance: PASS

This archive is a non-amending evidence mirror. It strengthens public availability and hash/time-anchor verification for physical-anchor evidence, but it does not alter the Covenant inscription or disclose confidential flaw challenge data.

What Public Evidence Can and Cannot Prove

Public evidence can support:

• P1 evidence package hash verification;
• P2 static image review;
• P3 recorded video review;
• P6 public flaw map comparison if sufficient macro/microscope data exists.

Public evidence alone cannot prove:

• live object existence at current time;
• onsite custody;
• touch/handling;
• confidential flaw challenge success;
• multi-party forensic attestation.

AI-generated image detection may be reported only as supporting evidence. It is not decisive.