VERIFY

Cryptographic verification

for every document published on this site.

Canonical Hashes

FORENSISM 2.0 : Future Provenance

SHA-256

e6b29251a959169319a0d5080b1a2a28aa13ff7840785eaf52358b8d6e5f54e8

Released June 25, 2026 · 132 pages

FORENSISM 2.0 : The Placement Letters

SHA-256

a492ab53f6a0869cb52fadd128a8211a870b04df08c354dd726fb4e3f0c3ba2e

Released June 27, 2026 · 11 pages

FORENSISM 1.0 : The Declaration

SHA-256

1b6cfa73e6d39842df20a9869d0f18314180a2543a91a26a44bb92c0d9ca30f3

Released March 19, 2026 · 27 pages

How to

Verify

Every flagship work in this body of work is hash-verified and OpenTimestamped on the Bitcoin chain. The .ots proofs are preserved in the chain-of-custody archive. Any reader can compute the SHA-256 fingerprint of a downloaded file and compare it to the published value.

Quick Steps to Get a SHA Hash

  1. Open Terminal: You can find it in Applications > Utilities, or just search for "Terminal" using Spotlight (Cmd + Space).

  2. Navigate to your file: The fastest way is to type shasum -a 256 (with a space at the end) and then drag and drop your file from the Finder into the Terminal window. The file's path will appear automatically. This avoids needing to type out the full file location.

  3. Run the command: Press Enter.

  4. Get your result: The Terminal will display the SHA-256 hash (a long string of letters and numbers) followed by the file's name.

  5. Compare the output: Match it to the hash listed above. If they match, the document is authentic and unaltered. If they don't match, the file has been changed in transit or is not the canonical version.

The hash is the receipt anyone can run. The test is public. The archive is provenance.

Mac

shasum -a 256 ~/Downloads/document.pdf

Windows (PowerShell)

Get-FileHash -Algorithm SHA256 "$env:USERPROFILE\Downloads\document.pdf"

Linux

sha256sum ~/Downloads/document.pdf

COMPANION VERIFY PAGES

archaeologicaldna.com/verify →

fibonaccidna.com/verify →

thehaiframework.com/verify →

What This

Proves

A SHA-256 hash is a cryptographic fingerprint of a file's exact bytes. Two files produce the same hash if and only if they are byte-identical. Even a single character changed anywhere in the file produces a completely different hash. The hashes above are published as the canonical record of each document at the time of its public release.

This page verifies integrity — that the document
you have is the document that was published.

What This

Doesn't

Prove

A hash alone does not prove authorship. It proves the bytes haven't changed. Authorship rests on the document's contents, the copyright recorded on every page, and the broader provenance record — the timestamped corpus history maintained at thehaiframework.com.

For Researchers and Journalists

The broader documentation record — including instance correspondence, OpenTimestamps proofs, and the corpus archive — is available to credentialed researchers under disclosure. Contact via the site's contact form.