Assessment, EU obligations
Assessment of the obligations, step by step. Every step has a control point, every claim an article, and the chain carries hashes so the work can be shown afterwards.
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
Step by step
- 1. Go through each obligation on the role and decide whether it reaches you. Can be shown: the list, with date and owner.
- 2. Read the recitals to the article before settling the interpretation. Can be shown: the role choice with one sentence on why.
- 3. Set a date: when does the requirement start to apply to you, per the timeline? Can be shown: the article rows with address, hash and reading date.
- 4. Assess the distance between the requirement and today's practice, in plain words. Can be shown: the gaps and what was decided about them.
- 5. Decide action, owner and time for every gap that remains. Can be shown: the next check date and who owns it.
Audit chain
- AI Act, 16: Obligations of providers of high-risk AI systems, af65a9ccb47f2b27
- AI Act, 9: Risk management system, 70f90ab846ebe962
- AI Act, 10: Data and data governance, 99a8715ef1812b45
- AI Act, 11: Technical documentation, d673275d86083b9c
- AI Act, 12: Record-keeping, fecf48d00c3486d3
- AI Act, 17: Quality management system, 4558a5030c303f26
- AI Act, 43: Conformity assessment, bbd005e288086663
- AI Act, 72: Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems, 0d0aa89a3cf2b185
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.
Roles
Articles
- AI Act, 16: Obligations of providers of high-risk AI systems
- AI Act, 9: Risk management system
- AI Act, 10: Data and data governance
- AI Act, 11: Technical documentation
- AI Act, 12: Record-keeping
- AI Act, 17: Quality management system
- AI Act, 43: Conformity assessment
- AI Act, 72: Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems
- AI Act, 73: Reporting of serious incidents
- AI Act, 26: Obligations of deployers of high-risk AI systems
- AI Act, 27: Fundamental rights impact assessment for high-risk AI systems
- AI Act, 23: Obligations of importers
- AI Act, 24: Obligations of distributors
- AI Act, 53: Obligations for providers of general-purpose AI models
- AI Act, 55: Obligations of providers of general-purpose AI models with systemic risk
- GDPR, 24: Responsibility of the controller
- GDPR, 25: Data protection by design and by default
- GDPR, 30: Records of processing activities
- GDPR, 32: Security of processing
- GDPR, 33: Notification of a personal data breach to the supervisory authority
- GDPR, 35: Data protection impact assessment
- GDPR, 28: Processor
- NIS2, 21: Cybersecurity risk-management measures
- NIS2, 23: Reporting obligations
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-skyldigheter/arbetsflode/bedomning?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-skyldigheter/arbetsflode/bedomning
- Layer
- index
- Read at
- 2026-08-31
- Freshness
- 41/100
- Checksum
- 8e94cdd470207ab1
- 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-skyldigheter/arbetsflode/bedomning, read 2026-08-31, checksum 8e94cdd470207ab1, corpus version legal-2026-11-02, license https://legal.exploreworldai.com/revision
- Owner
- Valkiv Ventures AB
- License
- https://legal.exploreworldai.com/revision
- Checksum
- 8e94cdd470207ab1
- Fingerprint
- ewai:eu:7ffcdf
- 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.