VERIFY

Cryptographic verification for every document published on this site.

Canonical Hashes

Archaeological DNA 2.0.pdf

SHA-256

473ee44f9346efc0b076a54e30635297b251f1cf7b42524163bd642e0c261807 
Released June 4, 2026 · 109 pages

How to

Verify

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

Compare the output 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.

COMPANION VERIFY PAGES

fibonaccidna.com/verify →

thehaiframework.com/verify →

FORENSISM.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.