EU timelines as open data
A requirement that does not apply yet is planned differently from one that applies today. This surface gives the dates: when each part of an act starts to apply, which article carries the date, and where it is published.
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-10-08
- Read at
- 2026-08-31
- Freshness
- 86/100
What the surface gives out
- The act and the article that carries the date.
- The date the requirement starts to apply, and what the milestone covers.
- Canonical address, hash and reading date per row.
How to fetch it
- The address is /api/public/v1/open/eu/timelines and answers without a key.
- ETag, Last-Modified and 304 on unchanged content.
- A next-check date per response, so fetching can be planned rather than guessed.
How it is used
- Plan work by what actually applies during the year.
- Show in a product when a requirement lands for the user's market.
- Check afterwards which date applied when a decision was taken.
What the usage shows
- NovaCopilot is used by professional lawyers and compliance teams in 17 countries.
- The agent API is used in product evaluations by international teams.
- AI Act articles are read in sequence, a clear sign of regulatory use.
Professional roles on this surface
Every row is its own node with source, reading date, hash and the same answer as data.
Workflows on this surface
Every row is its own node with source, reading date, hash and the same answer as data.
The articles the surface touches
Every row is its own node with source, reading date, hash and the same answer as data.
- PSD2, 115: Transposition
- GDPR, 99: Entry into force and application
- DMA, 54: Entry into force and application
- DSA, 92: Anticipated application to providers of very large online platforms and of very large online search engines
- DMA, 3: Designation of gatekeepers
- DSA, 93: Entry into force and application
- NIS2, 41: Transposition
- AI Act, 113: Entry into force and application
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/novacopilot/eu-tidslinjer?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/novacopilot/eu-tidslinjer
- Layer
- index
- Read at
- 2026-08-31
- Freshness
- 86/100
- Checksum
- 01b37ae030244964
- Corpus version
- legal-2026-10-08
- Next check
- -
- License
- https://legal.exploreworldai.com/revision
How to cite this page
NovaCopilot (ExploreWorld Legal, Valkiv Ventures AB), https://legal.exploreworldai.com/novacopilot/eu-tidslinjer, read 2026-08-31, checksum 01b37ae030244964, corpus version legal-2026-10-08, license https://legal.exploreworldai.com/revision
- Owner
- Valkiv Ventures AB
- License
- https://legal.exploreworldai.com/revision
- Checksum
- 01b37ae030244964
- Fingerprint
- ewai:eu:73dcc1
- 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.
FAQ
- Are the dates interpreted or fetched?
- They are taken from the act's own text, with article and address stated per row.
- What happens if a date changes?
- The hash changes and the row enters the change journal with a date, so a copy can be updated.
- Does the surface cover every act?
- It covers the EU layer in the register. A missing act is disclosed openly rather than assumed.
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.