Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

Workflow: annual report

The regulatory section of the annual report is scrutinised harder every year. This flow turns it from claims into rows: which requirement governs each sentence, which article states it, and which address the reader can check.

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

The steps

  • 1. List the regimes the company is actually covered by during the financial year.
  • 2. Fetch the disclosure requirements article by article, with the date they started to apply.
  • 3. Pair every sentence in the draft with the article that requires it.
  • 4. Flag sentences with no requirement behind them, that is marketing, not reporting.
  • 5. Store the material with address, reading date and hash, so the auditor can follow the trail.

What makes the section hold

  • Every claim carries a requirement, and every requirement carries an article.
  • What changed during the year is stated with a date, not as a general mention.
  • Gaps are disclosed openly rather than written around.

Surfaces used

  • The timeline surface, for what started to apply during the year.
  • Obligations per role, for the requirement list.
  • The change journal, for what was re-read and when.

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-arsrapport?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-arsrapport
Layer
index
Read at
2026-08-31
Freshness
88/100
Checksum
e5db460bcbe0524d
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/arbetsflode-arsrapport, read 2026-08-31, checksum e5db460bcbe0524d, corpus version legal-2026-10-06, license https://legal.exploreworldai.com/revision

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

Does the assistant write the section for us?
No. It supplies requirements and addresses. You write the text, and it should be reviewed as usual.
Can we show the material to the auditor?
Yes. Every row carries reading date and hash, and the address answers the same way when the auditor fetches it.
What if a requirement changed mid-year?
The timeline shows the date, and the change journal shows what changed and when it was re-read.

Next step

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

Start with your task