Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

Workflow: risk assessment

You make the assessment. This is the route there: which questions to answer in which order, which surface answers at each step, and what the material must carry to survive review.

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

The steps

  • 1. Describe the system factually: what it does, for whom, on which market and in which role you stand.
  • 2. Test role and market against scope before assuming anything else.
  • 3. Test the use against the prohibited practices, then against the high-risk annex.
  • 4. Fetch the duties that follow the role, article by article.
  • 5. Store the material with address, reading date and hash per row.

What the material must carry

  • The article number the requirement comes from, not just the name of the regime.
  • Reading date and hash per row, so the assessment can be checked a year later.
  • Whatever could not be supported, written out explicitly as a gap.

Surfaces used

  • The classification in the browser, for work done by hand.
  • The agent protocol for running the same steps from your own system, with a receipt per step.
  • The open obligations surface, when you only need the duty list per role.

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

Owner
Valkiv Ventures AB
License
https://legal.exploreworldai.com/revision
Checksum
381246cace060390
Fingerprint
ewai:eu:49f454
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

How long does the flow take?
A first pass takes minutes. The weight lies in describing the system honestly; the rest is lookup.
Can the flow be automated?
Yes. The same steps exist as an agent surface, with receipt, hash and versions per step.
What do we do with the gaps?
Write them into the material. A declared gap is a better basis for review than a filled-in assumption.

Next step

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

Start with your task