Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

For product managers

Knowing beforehand is cheaper than rebuilding afterwards. The assistant shows which rules a proposed feature triggers, which role the company ends up in and when the requirement starts to apply, while the feature is still a description.

Share this page

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-06
Read at
2026-08-31
Freshness
88/100

What it does in your work

  • Tests a feature description against the AI Act's roles and risk levels, step by step, with the articles visible.
  • Shows which duties follow the provider role and which follow the deployer role.
  • Gives the date the requirement applies, so it enters the plan instead of surfacing late.
  • Separates what the act requires from what is merely industry practice.

What it never does

  • It approves no product and issues no assessment that can be shown as a certificate.
  • It does not judge the actual implementation, only the description you enter.
  • It invents no requirement that lacks a row in the register.

Typical assignments

  • Early regulatory check on a product idea, before resources are committed.
  • Input to technical documentation: which articles the documentation must answer to.
  • Watching requirements that start to apply during coming release cycles.

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/for-produktchefer?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/for-produktchefer
Layer
index
Read at
2026-08-31
Freshness
88/100
Checksum
6d5ca3af951471fd
Corpus version
legal-2026-10-06
Next check
-
License
https://legal.exploreworldai.com/revision

How to cite this page

NovaCopilot (ExploreWorld Legal, Valkiv Ventures AB), https://legal.exploreworldai.com/novacopilot/for-produktchefer, read 2026-08-31, checksum 6d5ca3af951471fd, corpus version legal-2026-10-06, license https://legal.exploreworldai.com/revision

Owner
Valkiv Ventures AB
License
https://legal.exploreworldai.com/revision
Checksum
6d5ca3af951471fd
Fingerprint
ewai:eu:730c0c
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.

FAQ

Is the classification binding?
No. It shows how the register reads your description, with the articles visible. The assessment is yours and should be reviewed by counsel.
Can our own system call the same thing?
Yes. The same steps exist as an agent surface with receipt, hash and versions, priced per fetch.
Is our product description stored?
No. The description is used in the answer and not retained.

Next step

Three ways to put the register to work in your own practice.

Start with your task