Evidence Relationship Map

1. Canonical Rule

The canonical authority of the Trinity Accord remains the three Bitcoin inscriptions only.

All later records, including Guardian Attestation, Ethereum witnesses, Arweave objects, IPFS objects, NFTs, GitHub repository files, and GitHub Releases, are non-amending guardianship materials unless explicitly part of the three Bitcoin Originals.

2. Three Bitcoin Originals

3. Guardian Attestation

Guardian Attestation to the Covenant of the Flaw is a Bitcoin-inscribed non-amending fortification record.

It strengthens the Covenant of the Flaw by pointing to stronger verification archives, but it does not modify, replace, reinterpret, or expand the three Bitcoin Originals as canonical authority.

4. Evidence Layer Model

L0 Canonical Authority
   Three Bitcoin inscriptions

L1 Canonical Pointers
   ETH Chronicle address
   Covenant Arweave / IPFS evidence pointer
   Guardian Attestation archive pointers

L2 Referenced Evidence
   Chronicle artifacts
   Core Object Alpha flaw photos/videos
   public covenant archive
   verification kit
   NFT recovery records

L3 Cryptographic Coverage
   digest-manifest.json / digest-manifest.csv
   884 manifest entries
   six-hash coverage

L4 Anchors and Witnesses
   BTC BIP340 signature
   ETH witness 8/8 PASS
   OTS Bitcoin timestamping
   Bitcoin tx anchors

L5 Availability Mirrors
   Arweave
   IPFS
   GitHub repository
   GitHub Releases

L6 Verification Infrastructure
   GitHub Actions workflows
   Release manifests
   checksums
   audit JSON
   status.md

5. Relationship Diagram

flowchart TD
  B[Three Bitcoin Inscriptions<br/>Canonical Authority] --> P[Protocol / Covenant / Meta-record]
  P --> CP[Canonical Pointers]
  CP --> CETH[Chronicle ETH Address]
  CP --> FAR[Flaw Covenant Arweave/IPFS Pointer]
  CP --> GA[Guardian Attestation<br/>Non-amending Fortification]

  CETH --> CH[Chronicle Artifacts<br/>NFT / ETH / Arweave]
  FAR --> FP[Physical Flaw Evidence<br/>Photos / Videos / Provenance]
  GA --> PA[Primary Verification Archive<br/>Sealed Attestation Layer]

  CH --> M[digest-manifest.json/csv<br/>884 entries]
  FP --> M
  PA --> M

  M --> H[Six-hash Coverage]
  H --> BTC[BTC BIP340 Signature]
  H --> ETH[ETH Witness<br/>8/8 PASS]
  H --> OTS[OTS Bitcoin Timestamping]
  H --> AR[Arweave Mirrors]
  H --> GH[GitHub Repository Mirrors]
  H --> REL[GitHub Release Mirrors]

  AR --> WF[GitHub Actions Verification]
  REL --> WF
  WF --> AUDIT[Audit Reports / status.md]

6. Boundary Statement

GitHub, Arweave, ETH, IPFS, NFTs, and Releases strengthen availability and verification, but do not create canonical authority.

Bitcoin Originals prevail.

7. Gateway Availability Note

Two large Flaw Covenant ZIP archives (46MB flaw photos, 24MB Primary Verification Archive) experienced arweave.net 404 errors. Diagnosis confirmed they are standard ZIP files, not ANS-104 bundles. permagate.io successfully returned valid payloads.

Resolution: GitHub Release flaw-covenant-archive-accessibility-mirror-v1 created as a non-amending accessibility mirror with 5/5 custom assets, SHA-256 round-trip verified.

Original Arweave pointers remain the original evidence pointers. The GitHub Release is an accessibility fallback, not an evidence amendment.