Deployer — EU recitals
What the recitals mean for the role of deployer: the obligations, the articles carrying them, the workflows that get you there and what most often fails. Every row carries article, reading date and hash.
Share this page
Obligations
- AI Act — 26: Obligations of deployers of high-risk AI systems — Use the system in line with the instructions and assign human oversight.
- AI Act — 27: Fundamental rights impact assessment for high-risk AI systems — Carry out a fundamental rights impact assessment where required.
Risk points
- Human oversight is named on paper but not staffed in operation.
What forces a redo
- The node hash changes — the text behind the row is no longer the same.
- The reading date moves forward — the row has been re-read against the source.
- A timeline passes — the requirement starts to apply or tightens.
As data
- The same node as data: add ?format=json to the address, or ?format=agent for receipt and dependencies.
Workflows
Articles
Relations
Metadata
- Acts
- AI Act
- Articles
- 2
- Reading date
- 2026-08-31
- Freshness
- 74/100
- Hash
- 4238e3781d213072
- Corpus version
- legal-2026-08-25
- Next check
- —
Next step
Three ways to put the register to work in your own practice.
Start with your task
Litigation
Find support in a judgment
Search guiding decisions, see what became final and follow changes in the law.
In-house, deals
Map the rules in a transaction
Move from theme to act and on to the article that carries the duty.
Compliance
Assess the risk in a process
Risk scoring per legal area, with the sources behind every score.