How Veritome works

The EU AI Act compliance process, in six phases.

Know what each system owes, then do it in six phases. A deterministic engine decides the obligations; the GDPR and standards run beside it.

Deterministic · Article-anchored · EU-hosted
The engine underneath

The rules engine behind your EU AI Act compliance process.

It reads each system's role and risk tier and returns only the obligations it owes. No language model decides them.

Obligation registerDerived by the engine
13obligations applyDeployerHigh

13 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register1
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend & notify on serious risk
Art. 26(9)Use Art. 13 information for the GDPR Art. 35 DPIA
Computed by the engine for one system · switch the role to compare
01

Deterministic results

Same inputs, same obligations: what you tell an auditor today still holds tomorrow.

02

Anchored to the article

Every obligation and deadline cites the provision it comes from.

03

Kept current in one place

When the law changes, we update the engine and affected systems update with it.

The engine's logic is our intellectual property; the article behind every obligation is yours to audit in full.

The EU AI Act path

From first classification to live monitoring, in six phases.

Every system takes the same gated path. A phase with nothing for your role passes automatically.

System journeyCredit-scoring model
HighProvider
Classify1/1Done
Scope & literacy3/3Done
Build & document4/9In progress
Conformity assessment0/4To do
Register0/2To do
Operate & monitor0/6To do
EU AI Act journey
8of 25 done
GDPR duties on this system
2of 3 done
Conformity assessment opens when Build & document closesThe next step is always clear
Illustrative record · articles are real, the system is not
01

Classify

Know exactly what you are holding.

Answer a short set of questions per system and get its risk tier, with the articles that decide it.

Art. 5Art. 6Annex III
02

Scope

See only the obligations that apply to you.

Your role and risk tier decide the list: a chatbot deployer and a high-risk provider get different ones.

Art. 16–27Art. 25
03

Implement

Put the measures in place, with the proof attached.

Work through each obligation as a guided checklist, attaching evidence that carries an expiry date.

Art. 9–15Art. 26
04

Assess

Run the assessments the Act requires, on the record.

Guided FRIA and conformity assessments end in a sealed report; overlap with an existing DPIA is mapped.

Art. 27Art. 43Annex IV
05

Register

Hand over a dossier traced article by article.

Annex VIII fields pre-filled, a Declaration of Conformity and a hash-sealed dossier with a public verify URL.

Art. 47Art. 49Annex VIII
06

Monitor

Keep the obligations current after the system goes live.

Post-market monitoring, serious-incident reporting, scheduled reviews and a watch on changes in the law.

Art. 72Art. 73
The standards on top

Switch a standard on and it becomes a programme.

ISO/IEC 42001, ISO/IEC 27001 and NIST AI RMF are yours to enable. Each becomes a programme with its own page.

One record per step, and a step your other work covers is marked Done, credited. The certificate comes from an accredited body, never from us.

The five frameworks and their crossover
ISO 42001ISO 42001 programme
27 steps · 6 phases · one record each
01Establish
5 steps · Complete
02Plan
5 steps · In progress
03Support
3 steps · Locked
04Operate
8 steps · Locked
05Evaluate & improve
4 steps · Locked
06Certification audit
2 steps · Locked
Plan · the steps
  1. 01Risk methodology and AI risk assessmentAlso counts toward ISO 27001Done
  2. 02Risk treatment and Statement of ApplicabilityIn progress
  3. 03AI system impact assessmentTo do
  4. 04AI objectives and planning to achieve themAlso counts toward ISO 27001To do
Phases and steps as the product generates them · progress shown is illustrative
Statement of ApplicabilityISO/IEC 42001 · Annex A
A.2.2AI policy
Adopted by the board; reviewed yearly.
A.5.2Impact assessment process
Impact assessed per system before deployment.
A.6.2.6Operation and monitoring
Justification missing
A.10.4Customers
We supply no AI system or service to customers.
1 to justifyTry a decision · nothing is saved

ISO/IEC 42001 is a voluntary standard. Certification against it confers no presumption of conformity under Article 40 of the EU AI Act; harmonised standards, once cited in the Official Journal, are the only route to that presumption.

Illustrative statement · the controls are Annex A’s
Straight answers

What the engine will and will not do

Answered as the product ships today.

Is the obligation mapping done by an AI model?

No. A deterministic rules engine maps role, risk tier, Annex III area and behavioural flags to the obligations, each citing its article. Aria drafts and proposes; it never decides a classification or files anything.

What happens to the other frameworks?

The EU AI Act and the GDPR are statutory and always on. ISO/IEC 42001, ISO/IEC 27001 and NIST AI RMF are voluntary programmes. A record you already have is credited where it satisfies an ISO clause.

Can I skip a phase?

No. Phases are gate-locked, so you cannot register a system you have not assessed. A phase with nothing that applies to your role is complete by definition.

Is any of this legal advice?

No. Veritome structures the work and cites the law; the judgement calls are yours and your counsel's. Every screen names the article it rests on.

Want the article-by-article view? Read the EU AI Act guide.