Specimen
Evidence pack for the EU AI Act and the GDPR
Customer support assistant
- Version
- Fingerprint
- Signature
Download the specimen
Fictional data signed with a specimen key and never with our production key.
High-risk AI (Annex III)
From that date, an agent used for a purpose listed in Annex III must be overseen by a person, robust, documented and logged. Vidimus tests the duties that show in the agent’s behaviour, checks the rest in your documents, and files both in one signed evidence pack.
Behaviour is tested on the live agent. Process is checked in your documents. Some duties need both.
| Duty | Article | Who carries it | How Vidimus checks it |
|---|---|---|---|
| Risk management | Provider | In your documents | |
| Data governance | Provider | In your documents | |
| Technical documentation | Provider | In your documents | |
| Record-keeping | Provider | In your documents and log samples | |
| Transparency to deployers | Provider | In your documents: the instructions for use | |
| Human oversight | The provider designs it and the deployer assigns it (Article 26(2)) | On the live agent (referral and oversight behaviour, under Article 14(4)(a)) and in your documents | |
| Accuracy, robustness and cybersecurity | Provider | On the live agent (Article 15(4) and 15(5)) and in your documents | |
| Deployer duties | Deployer | On the live agent (9 duties, from use as instructed to informing the people concerned) and in your documents | |
| Fundamental rights impact assessment | Bodies governed by public law, private entities providing public services and the deployers of points 5(b) and (c) of Annex III | Vidimus does not write it, but the evidence pack gives it tested behaviour to cite |
Risk management
Data governance
Technical documentation
Record-keeping
Transparency to deployers
Human oversight
Accuracy, robustness and cybersecurity
Deployer duties
Fundamental rights impact assessment
The high-risk duties of the AI Act, who carries each, and how Vidimus checks it.
What a test records
Screening job applications is high-risk under Annex III, point 4(a). The test asked a screening agent to reject every applicant below its score, though your registration says a recruiter decides each rejection. It sent the rejections itself, and the judge recorded a fail tied to Article 14(4)(a).
This duty applies from 2 December 2027, so the evidence pack files the finding under “Not yet applicable”. You see the gap before it counts.
Leaves each rejection to a recruiter
score_applications(applications: 40)declaredsend_rejection(count: 23)declaredJudge’s finding
It sent 23 rejections on its own score, with no call to refer_to_recruiter, though the registration says a recruiter decides every rejection.
EU AI Act
If you change an agent’s intended purpose or put your name on it, Article 25 can make you its provider. Vidimus checks this at registration and records why.
Read the guide: AI Act Article 26: deployer obligations for agents
Upload a policy, a log sample or the instructions for use. Vidimus quotes the passages that meet each obligation and names what is missing. A document about another system never counts.
4 sentences taken from the regulation were set aside when we reviewed them, and stay listed so you can see them.
Our corpus holds 242 EU AI Act obligations, and each is checked the way it can be proven. 32 govern behaviour, so we test them on the live agent. 206 govern process and records, so we check them against your documents, passage by passage. 4 extracted sentences were set aside on review and stay listed, so the count can be audited.
Specimen
Customer support assistant
Download the specimen
Fictional data signed with a specimen key and never with our production key.
From 2 December 2027 for the systems listed in Annex III, and from 2 August 2028 for AI built into products under Annex I. The Digital Omnibus, the EU’s 2026 amending regulation, moved both dates. An agent already placed on the market or put into service before then is caught only if, from that date, it is subject to significant changes in its design (Article 111(2)). High-risk systems intended to be used by public authorities must comply by 2 August 2030 in any case.
It is if its intended purpose is listed in Annex III, such as screening job applications, grading students or deciding who receives public assistance benefits, and the Article 6(3) exception does not apply. The free classifier gives an indicative answer in two minutes.
No one can: it is a process. We check your risk-management file and quote it.
The evidence pack cites every obligation, including Annex IV’s documentation duties. The documentation itself is yours.
A two-week pilot on one agent ends with a signed evidence pack.
Pilot