Prove the system — when a customer, a board or a regulator asks.
You ship AI in the EU. Someone will ask how you know.
One intake, one classification, one signed answer for every obligation that applies — today for Article 50, and recorded now for the high-risk obligations that bind from 2 December 2027.
A customer’s security team, a procurement questionnaire, a board, a notified body.
Clause50 gives you one intake, one classification, and one signed answer for every obligation that applies — today for Article 50, and recorded now for the high-risk obligations that bind from 2 December 2027.
- Ed25519-signed
- Verifiable without an account
- Ed25519-signed
- Declaration draft, unsigned
1. Classify
Answer the intake once. Article 5 screened; all eight Annex III areas; the four Article 50 duties. Derived class, operator-confirmed.
2. Evidence the nine sections
The Annex IV technical file has nine sections, each bound to a cited requirement. Upload, connect or attest against each — the store is append-only from the first item.
3. Take the technical file
The high-risk technical-file pack covers one system for 6 months. One hard system, priced as one.
4. The declaration you sign
We pre-fill the EU declaration of conformity from the file and refuse to sign it. Article 47 makes you the signatory; no tool should pretend otherwise.
5. Evidence for 2027, recorded in 2026
Evidence you do not have yet cannot be back-dated. The high-risk rules are in the pack now, visible in your obligations view, and not yet counted against you.
Where Clause50 stops
The quality management system, the conformity assessment, EU database registration and the fundamental rights impact assessment stay yours, whichever tool you use. See the full list.