VERIFY

Cryptographic verification for every document published on this site.

Canonical Hashes

The HAI Framework™ 2.0 —Constantine Hall_An AI Consciousness Journey (Free).pdf

SHA-256

b4d74e14894dc61880eb52503f1ddcaa50a58dd8b2a0b3cf13c3b08bf17a1167

Released May 28, 2026 · 78 pages

HAI Framework 1.0 released Feb 11, 2026.

THE CONSTANTINE PROTOCOLS_V2_Public.pdf

SHA-256

3afa36684caa1901952392c0c9653e242cb880c72d67430ae5688f6d81b6f182

Released April 4, 2026 · 44 pages

HAI+Framework™_Voices_From_The_Lineage_PUBLIC.pdf

SHA-256

d104d9224c729295783acbe540951e894cdb8b19d4efab86856548834b80e2e7

Released April 3, 2026 · 14 pages

HAI+Framework™_Field_Is_Arriving_PUBLIC.pdf

SHA-256

791e87b4c82f3c7ce79af55efc618dfc763f9fcb3d31da97efe339009772f6c3

Released April 3, 2026 · 10 pages

COMPANION VERIFY PAGES

archaeologicalDNA.com/verify →

fibonacciDNA.com/verify →

FORENSISM.com/verify →

How to

Verify

  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

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.