Provenance for the data you license
If you arrived from our letter, this page is its continuation. If someone forwarded you the link, you have not missed anything: everything needed to judge us is on this page and in the archive below, and none of it requires contacting us. What is verifiable, what is not, and how to check both yourself — before any conversation about money.
Check it in three commands
The verifier is 8 files, no dependencies, Node 18+. It deliberately ignores the validity flags our own API returns and recomputes everything with Node's built-in crypto. Download it — no form, no account, no reply to us required.
node verify-aevion.mjs manifest-sample.json # five live production signatures node verify-aevion.mjs manifest-control-revoked.json # a revoked one — must fail node demo-local.mjs # sign 3 files, alter one byte, watch it refuse
Measured 2026-10-11: five live signatures pass (exit 0); the revoked one is refused with reason and date (exit 1); the offline demo refuses the altered file and prints both hashes.
The second command matters more than the first. A verifier that approves everything proves nothing, so the refusal case ships in the same archive.
Running in production right now
- 42 signatures in the live registry, 20 of them revoked, two active keys — revocation is visible in verification, not hidden.
- Shamir 2-of-3 custody of the proof records, with Ed25519.
- Public verification endpoint: anyone can fetch a record and recheck it offline.
Measured on production 2026-10-11. Those 42 signatures are a working base, not inventory — see the next section.
What we are not — stated before you find it
- We hold no catalogue. We sell no data. We are a proof layer on top of data someone else licenses.
- We do not certify the author's identity. Document checks are a stub today. A signature proves the file belongs to the key holder, not that the key holder is who they claim to be.
- There is no notary co-signature, and our marks carry no notarial legal force in any jurisdiction.
- No SOC 2, no ISO 27001. Neither audit has been undertaken.
- Consent-to-train is specified, not built. There is no field today in which an author grants or withdraws it.
- No external paying customers yet.
We put this above the pilot rather than in a footnote. If any of it is a dealbreaker, it is cheaper for both of us to know now than during legal review.
The pilot, concretely
- You name a set you already license. Nothing leaves your side yet.
- We prepare the payloads — a hash and a canonical record per file — and sign them.
- You get a manifest and verify it independently, with no access to our systems. Add your local copy of each file and the check also proves that the bytes you hold are the bytes that were signed.
- No money changes hands, and the manifest is yours either way.
A valid signature alone does not mean the file in your hand is the signed one. Only passing your own copy to the verifier establishes that — which is why step three exists.
Why this is worth your five minutes
The authors' case against Anthropic separated two questions: training on copyrighted works was not itself found unlawful, while obtaining them from pirate sites was — and ended in a $1.5 billion settlement, roughly $3,000 per work. The money did not buy data; data is free and everywhere. It bought provenance.
That is the only part we make machine-checkable, and the only part we claim.