Deployer, EU timelines
What the timelines 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.
NovaCopilot · ExploreWorld Legal
European and Nordic law as verifiable data, with source, reading date and checksum on every row.
- Publisher
- NovaCopilot, ExploreWorld Legal
- Corpus version
- legal-2026-11-02
- Read at
- 2026-08-31
- Freshness
- 41/100
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
The NovaCopilot models
The decision model
In: A role, a legal act and the situation in plain words.
Out: The obligations that reach the role, the article behind them and what remains.
When: When the question is whether a requirement applies to you, and why.
The difference model
In: A checksum already used and the date of the last reading.
Out: What changed since then: checksum, reading date, passed deadline and rows to revisit.
When: When earlier work is reused and has to be checked first.
The obligation model
In: A legal act or an article, with or without a role filter.
Out: The obligation in the register's wording, the role it reaches, canonical address and reading date.
When: When the answer has to be citable article by article.
Example for an agent
curl -s "https://legal.exploreworldai.com/en/novacopilot/eu-tidslinjer/roll/deployer?format=agent"- canonical, the address to cite
- node_hash, the checksum for the next comparison
- corpus_version, the corpus version that answered
- freshness.read_at, the reading date of the row
- freshness.next_check, when a new check is reasonable
- citation.string, the finished citation
- agent.receipt, the receipt of the call, without a key
Metadata
- Canonical address
- https://legal.exploreworldai.com/en/novacopilot/eu-tidslinjer/roll/deployer
- Layer
- index
- Read at
- 2026-08-31
- Freshness
- 41/100
- Checksum
- 3499da64d0e003d2
- Corpus version
- legal-2026-11-02
- Next check
- -
- License
- https://legal.exploreworldai.com/revision
How to cite this page
NovaCopilot (ExploreWorld Legal, Valkiv Ventures AB), https://legal.exploreworldai.com/en/novacopilot/eu-tidslinjer/roll/deployer, read 2026-08-31, checksum 3499da64d0e003d2, corpus version legal-2026-11-02, license https://legal.exploreworldai.com/revision
- Owner
- Valkiv Ventures AB
- License
- https://legal.exploreworldai.com/revision
- Checksum
- 3499da64d0e003d2
- Fingerprint
- ewai:eu:031466
- Terms
- Use, cite, index and cache. The register as such is not resold.
Source registers
The same material as registers, with read date and source on every row.
French edition
The same node in French, with the same read date, checksum and citation.
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.