Meridian-Canon

A Canon for Falsifiable Digital Evidence

J. Patrick White

This book is about a problem that did not exist twenty years ago and is not yet solved: how to make personal digital evidence verifiable by its recipients, without requiring them to trust the system that produced it.

The answer is a cryptographic attestation format called the Canon. Every numbered chapter in this book builds one piece of it: the hash function that binds bytes to identity, the signature that binds identity to a signer, the canonicalization scheme that makes the signature deterministic, the schema that constrains what a claim may say, the pipeline that carries a document from receipt to sealed attestation, and the verifier that any recipient can run — independently, without cooperation from the issuer — to check that nothing has changed.

By the end of the book, you will have built a working evidence system over a corpus of your choice, produced Canon-conformant attestations for it, and implemented a standalone verifier in a second programming language that agrees byte-for-byte with the Python reference.

How to read this book

See How to read this book and the Reading paths matrix for audience-specific sequences. The Syllabus maps the book to a 15-week course.

The running case

Every chapter returns, where possible, to the same case: a parent in a 2026 termination of parental rights proceeding whose evidence is distributed across six personal-data systems, and whose attorney has fifteen minutes to find ten specific messages. The case is fictional in detail and composite in nature. Its purpose is to make the abstractions concrete.

The canonical artifact

The book is organized around a single artifact — a sealed Canon attestation — that the reader constructs, one layer at a time, across all thirty chapters. By Chapter 25, the attestation produced in Chapter 4 can be independently verified by a Go program the reader wrote themselves.

Part I — Foundations (Why) begins on the next page.