If a single bit changes, you know.
You know how when you seal an envelope, you can tell if someone opened it? The seal is broken. You know it was tampered with.
Integrity does that for your digital stuff.
Every piece of data you store gets a unique fingerprint — like a wax seal. That fingerprint depends on every single letter, every number, every space. Change one character and the fingerprint breaks. We chain those fingerprints together so you can check everything at once: did anything change? Who changed it? When?
This matters because most companies say "we won't change your data." That's a promise. Promises get broken. Integrity replaces the promise with proof. You don't have to trust us. You can check for yourself.
What does "open source" mean? It means this code is public. You can read every line. You can run it yourself. You can have an expert you trust review it. We're not asking you to take our word for it — we're showing you the receipts.
Read the manifesto: ai-pantheon.ai
Every system that stores data makes an implicit promise: we won't change your stuff. Most systems enforce that promise with access controls — rules that can be rewritten by anyone with admin access.
Integrity enforces it with math. Every piece of data gets a cryptographic fingerprint. Those fingerprints chain together into a Merkle tree. If anything changes — a single character, a single byte — the tree breaks and the system knows.
This repository contains:
| Component | What It Does |
|---|---|
| Hash Chains | Sequential integrity verification — every entry links to the one before it |
| Merkle Trees | Tree-based verification — prove any single item hasn't been tampered with without checking everything |
| Signature Validation | Ed25519 signature verification — prove who wrote it and that it hasn't changed |
| Audit Trails | Immutable logs — every action recorded, every record verifiable |
If you're not technical: Imagine every page of a notebook has a unique stamp that depends on everything written on that page and the stamp from the previous page. If someone tears out a page, changes a word, or inserts something new — every stamp after it breaks. You can always tell if something was tampered with, and exactly where.
If you want the details: SHA-256 hash chains with Merkle tree verification. Ed25519 signatures for provenance. Append-only audit logs with cryptographic linking. The verification is independent — you don't need to trust the server, you verify locally.
Document A ──hash──> H(A)
│
Document B ──hash──> H(B)──┐
├──hash──> H(AB)
Document C ──hash──> H(C)──┐ │
├──hash──> H(CD)──┐
Document D ──hash──> H(D)──┘ ├──> Root Hash
│
Change one byte in Document C? │
H(C) changes. H(CD) changes. │
Root hash changes. │
Tampering detected. ✗
- Nothing changes silently. Every modification breaks the hash chain. There is no way to alter data without detection.
- Provenance is provable. Ed25519 signatures prove who created each entry and when. Signatures can't be forged.
- Verification is independent. You don't trust the server. You verify the chain yourself, locally, with open code.
Integrity works alongside Identity and Safety — the three open-source pillars of the Pantheon platform.
| Pillar | What It Does |
|---|---|
| Identity | Prove it's yours — cryptographic key management and data sovereignty |
| Safety | No one reads it but you — client-side encryption and anonymization |
| Integrity | No one changed it — tamper detection and audit trails |
AGPL-3.0 — You can use, modify, and distribute this code. If you modify it, you must share your modifications under the same license.
See LICENSE for the full text.
- Security researchers: Break it. Find weaknesses. File issues.
- Cryptographers: Review the hash chain implementation. Suggest improvements.
- Engineers: Integrate it into your own systems. Report what works and what doesn't.
Read the manifesto: ai-pantheon.ai
If it changed, you'll know. That's the point.