You don’t have to trust Clause50 to verify a Clause50 artifact.
Evidence, in this product, is a record of what was true about an AI system, bound to the obligation it answers, that cannot be edited afterwards and can be checked by anyone. This page is the whole idea in one place — and a real artifact to check.
A real artifact, for you to check
Below is a complete Article 50 evidence pack for a fictional energy retailer’s support chatbot, and a risk classification memo for a fictional agency’s image generator with four open gaps. Both are signed with our specimen key and marked “specimen — not evidence” on every page; both verify at /verify.
Article 50 evidence pack — Ostrahaven Energy (specimen)
A support chatbot, one open gap.

Risk classification memo — Sablewick Studio (specimen)
A campaign image generator, high-risk-adjacent, four open gaps.

Each ZIP contains the signed document (DOCX + PDF), the manifest bundle (manifest-bundle.json), and a VERIFY-THIS-PACK.md with the steps to check it yourself, offline. Upload manifest-bundle.json at /verify to see it verify live.
Follow one requirement through the specimen
Pick a requirement from the Ostrahaven pack. Below it: the evidence it rests on, that evidence’s hash, the entry in the signed manifest, and what /verify says about the whole pack.
3 more requirements are not applicable to this system, and say so in the document.
Read from the signed document of Ostrahaven Energy (specimen)’s demo — support assistant (chatbot), rule pack 2026.19.
- 2-ostrahaven-assistant-disclosure-v1.pdfDoc upload · in the pack's evidence/ folder · recorded 18 Sept 2026
- Attestation — a statement, not a fileIts full text is in the document's evidence register · recorded 18 Sept 2026
- Content hash — the evidence chain’s hash of the whole item
7290d41d48d23b5e035db7f2151e4cb03db53c9303588045c2b031578a8984e9File sha256 — re-compute it yourself withsha256sum0dc707eab5591a7703aaaf50bf1455daff435de9f43e2a6838a24736f8411bbb - Content hash — the evidence chain’s hash of the whole item
9ac43a7845d091055765c5aa27fd919f3b2efb22d1d35dd3bcb4dbca04a29f50
{
"id": "cmu6ekd53000aga1k3tlvemm4",
"recordedAt": "2026-09-18T03:32:22.023Z",
"contentHash": "7290d41d48d23b5e035db7f2151e4cb03db53c9303588045c2b031578a8984e9",
"requirementKeys": [
"disclosure_implementation"
]
}{
"id": "cmu6ekdjj0028ga1k92zzrh1s",
"recordedAt": "2026-09-18T03:32:22.543Z",
"contentHash": "9ac43a7845d091055765c5aa27fd919f3b2efb22d1d35dd3bcb4dbca04a29f50",
"requirementKeys": [
"disclosure_implementation"
]
}As it appears in manifest-bundle.json, signed with the key key-specimen-test.
- Manifest found
- Key in registry
- Signature valid
- Markdown matches
- DOCX matches
- PDF matches
- Specimen claim agrees with key
Valid signature — this is a Clause50 SPECIMEN document, generated from a demo system. It has not been altered since it was generated, and it is NOT evidence about any real AI system.
Download this pack and check it at /verify — the result above is what that page says about it.
What “EU AI Act evidence” means
An obligation names what must be true. Evidence is what shows it was — a document, an attestation against a checklist, a record pulled from a connected system, or an event your own systems sent. Each is bound to the requirement it answers.
The lifecycle
Where evidence comes from
Uploads, attestations, read-only connectors (usage reports from your model provider, a repository, an S3 log export) and an ingest API. Capability level only — the setup is in the product.
- Every requirement cites its evidence by hash
- Manifest bundle inside the ZIP
Obligation → evidence
Every requirement in a signed document names the evidence its status rested on, by content hash — not a summary written afterwards.
- This requirement's status cites this hash
- Ed25519-signed manifest over the whole bundle
- Verifiable at /verify without an account
Kept, then signed
Append-only, by construction
No update, no delete — enforced in CI, migrations included. A mistake is retracted with a new entry that says so; the original stays.
Signed
Every finalised artifact carries an Ed25519-signed manifest over the whole bundle.
Verification — what it proves, and what it does not
It proves the bundle you hold is byte-for-byte what Clause50 signed, and when. It does not prove the evidence is true, complete, or that the system is compliant — those are the operator’s statements, and the document says whose they are.
- Ostrahaven Energy · specimen
manifest-bundle.json- Manifest found
- Key in registry
- Signature valid
- Markdown matches
- DOCX matches
- PDF matches
- Specimen claim agrees with key
What stays yours
- The quality management system (Article 17) — operating it stays yours; we record its documentation now, for the duty that applies from 2 December 2027.
- Conformity assessment (Article 43).
- EU database registration (Articles 49 and 71).
- The fundamental rights impact assessment (Article 27).
- Running post-market monitoring (Article 72) — we evidence what you did.
- Running Article 4 AI-literacy measures — we record what you did.
- Following your Article 26 deployer duties — we record your evidence of them now, for the duty that applies from 2 December 2027.
- Signing the declaration of conformity (Article 47).
Clause50 is an EU AI Act evidence platform. It classifies an AI system against the whole Act from one intake — prohibited practices under Article 5 are refused, high-risk systems are screened against all eight Annex III areas and documented across the nine sections of the Annex IV technical file, and the four Article 50 transparency duties are evidenced — and it answers every obligation that applies with append-only, Ed25519-signed evidence that anyone can verify without an account. It records evidence against the 2027 high-risk obligations today, so the file exists on the day they bind — or on the day a significant change brings a legacy system into scope. It pre-fills the EU declaration of conformity and refuses to sign it. It is not the quality management system, conformity assessment, EU database registration or the fundamental rights impact assessment — those stay yours, whichever tool you use.