Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

For procurement and purchasing

A requirement you cannot check is not a requirement. The assistant brings up the regime behind it and shows what disclosure can actually be reviewed once the bids arrive.

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

Material before the tender

  • AI Act duties per risk class, so the requirement cites the article rather than an interpretation.
  • Data protection, information security and sustainability with source and entry into force.
  • US and European regimes side by side when the supplier sits outside the EU.

At evaluation

  • A system card is a disclosure at a fixed address, it can be re-read and compared between bids.
  • Read dates and the change journal let you show which state of the rules the requirement was written against.
  • The same node in four languages, so bidders in several countries read the same text.

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-upphandling?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-upphandling
Layer
index
Read at
2026-08-31
Freshness
87/100
Checksum
7b799b32030a2b4d
Corpus version
legal-2026-10-07
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-upphandling, read 2026-08-31, checksum 7b799b32030a2b4d, corpus version legal-2026-10-07, license https://legal.exploreworldai.com/revision

Owner
Valkiv Ventures AB
License
https://legal.exploreworldai.com/revision
Checksum
7b799b32030a2b4d
Fingerprint
ewai:eu:5776f0
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

Can we cite a node in the tender documents?
Yes. The addresses are fixed and the pages open, but the requirement should always also point at the official source behind the node.
Does the assistant assess a bid?
No. It shows the regime and what it requires. The evaluation belongs to the contracting authority.
What makes a system card a usable requirement?
It is a published disclosure at a fixed address with a hash, so the same card can be checked again afterwards.

Next step

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

Start with your task