Skip to content
Clause50EU AI Act evidence — starting with Article 50.EU AI Act evidence, starting with Article 50
Sign in
How Clause50 works

Rules decide. Evidence proves. You sign.

Clause50 builds the record you show when someone asks how your AI system meets the EU AI Act — and anyone you send it to can check it.

Start free →See a signed specimen →
The method

Three layers, each with one rule.

Rules decideA versioned rule pack, cited to the article text, turns your answers into a risk class and the obligations that apply. The same answers, against the same rule-pack version, give the same risk class. No model makes that call.
Evidence provesDocuments, read-only connectors and checklist attestations enter an append-only store, each item hash-chained to the one before it. Every requirement in the signed document names the evidence its status rested on.
You signClause50 seals the record with its own signature, so anyone can check it was not edited. Signing the EU declaration of conformity stays yours: we draft it and refuse to sign it.
Where models stop

What no model does in Clause50

  • Classify your system.
  • Decide which obligations apply.
  • Score your coverage.
  • Assemble your document or seal it.

Each line is asserted by a test that fails if that code can reach a model. Models may help author the rules. They never decide the evidence.

Check it yourself

Don’t take our word for it.

Our public specimens are signed with a separate specimen key and marked “specimen — not evidence” on every page. Download one and verify it the way your auditor would.

Explore a real, signed specimen, then verify it →Verify any Clause50 document — no account needed →Security in depth →

What we don’t claim

Clause50 assembles evidence toward your obligations. It is not the compliance programme, and no software is.

  • Not legal advice.
  • Not a certification.
  • Not a conformity assessment, and not a notified body.
What the pack covers today

Rule pack 2026.27 · 6 obligations in force · 18 modelled for 2 December 2027 · nine Annex IV sections, each bound to a cited requirement. What binds now is separated from what binds later — in the product, in the signed document, and here.

Clause50 records evidence today toward the obligations that bind from 2 December 2027, so the file exists on the day they bind — or on the day a significant change brings a legacy system into scope.

Every rule, every date, every requirement →
Where Clause50 stops

What Clause50 proves. What stays yours.

Clause50 assembles evidence toward your obligations. It is not the compliance programme, and no software is. Saying exactly where the line sits is the point.

Clause50 proves

  • The risk class, derived from your answers and confirmed by you.
  • Which obligations apply — in force and from 2 December 2027.
  • The Article 50 evidence pack, with the evidence behind each requirement by content hash.
  • The Annex IV technical file and an unsigned declaration draft — signed, verifiable without an account.

Stays yours, whichever tool you use

  • The quality management system (Article 17).
  • Conformity assessment (Article 43).
  • The fundamental rights impact assessment (Article 27).
  • Signing the declaration of conformity (Article 47).

EU database registration and running post-market monitoring stay yours. Article 4 AI literacy measures are recorded once for your organisation, and Article 26 deployer duties for each system you deploy; carrying them out stays yours.

The full list, with what each one means →

Not available today: single sign-on (SSO).

Start with one system.

Free to classify a system and read your coverage.

Start free →