1. The Problem: Why Vector-Only Compliance Tools Fall Short
The EU AI Act is not a checklist. It is a layered regulatory instrument with 113 articles, 13 annexes, and a dependency graph of obligations that spans prohibited practices, risk-tiered requirements, conformity assessment procedures, and ongoing monitoring obligations. Answering a question like "does my AI system require a conformity assessment under Article 43?" requires reasoning across Article 6, Annex III, Annex IV, Articles 43 and 49, and the recitals that clarify intent — simultaneously.
Vector-only Retrieval Augmented Generation (RAG) — the architecture underlying most AI compliance tools — retrieves semantically similar text chunks and asks an LLM to synthesize an answer. The approach works well for isolated factual lookups. It fails systematically for multi-hop regulatory reasoning because it cannot follow relational paths through the regulatory graph. A vector retriever returns the most similar text to your query, not the most relevant path through the obligation network.
The practical point does not depend on a benchmark score: when a compliance tool cannot show the path behind an answer, every gap analysis, risk classification and documentation recommendation has to be checked by hand.
This is the problem TraceGov.ai was built to solve. Not by deploying a better LLM — but by changing the fundamental architecture of how regulatory knowledge is represented and reasoned over.
2. TAMR+ Methodology: Temporal-Adaptive Multi-hop Reasoning
TAMR+ — Temporal-Adaptive Multi-hop Reasoning — is the core reasoning methodology developed at Quantamix Solutions and published as SSRN 6359818. The methodology is covered by pending European patent application EP26162901.8. It addresses three specific limitations of vector-only RAG for regulatory compliance:
Limitation 1: Single-hop retrieval
Vector RAG retrieves the single most similar document chunk to a query. EU regulatory obligations typically span 3–7 interconnected provisions. TAMR+ resolves this by performing multi-hop graph traversal: starting from an anchor node (e.g., the article most relevant to your query), it follows defined relation types — implements, derogates-from, cross-references, clarifies — to retrieve the full obligation network relevant to the question.
Limitation 2: Static knowledge
Standard RAG indexes documents once. Regulations evolve: delegated acts, implementing regulations, guidance documents, and EDPB/AI Office opinions all modify the effective compliance landscape after the base regulation is indexed. The "Temporal-Adaptive" component of TAMR+ implements a versioned graph where every node carries an effective-from and effective-to timestamp, allowing the platform to answer compliance questions for a specific point in time or to flag where a previous answer is no longer valid.
Limitation 3: Lack of reasoning transparency
LLM outputs from vector RAG systems are opaque: the system returns an answer but cannot show the precise regulatory path it followed to reach that answer. TAMR+ traversal is fully auditable — every compliance answer is accompanied by the graph path that produced it, showing which articles, annexes, recitals, and guidance documents were traversed, in what order, and what inference was made at each hop. This path becomes the audit trail for regulator-facing documentation.
3. Architecture: 31 OWL Entity Types and Regulation-as-Graph
The TraceGov.ai knowledge graph represents EU regulations using 31 OWL (Web Ontology Language) entity types. The ontology is structured in three layers: regulatory structure, obligation semantics, and entity binding.
Regulatory Structure Layer
This layer captures the document structure of EU regulations: Recital, Chapter, Section, Article, Paragraph, Subparagraph, Annex, Implementing Act, Delegated Act, Guidance Document, and Standard. These nodes are connected by structural relations: precedes, contains, implements, and supersedes. Structural traversal allows the platform to retrieve all provisions that are part of a specific obligation set — for example, all provisions governing high-risk AI systems across the main regulation text, its annexes, and subsequent implementing acts.
Obligation Semantics Layer
This layer captures the semantic content of obligations: ObligationNode, ProhibitionNode, ExemptionNode, ConditionNode, DeadlineNode, ThresholdNode, RoleNode, and ProcessNode. An obligation like "providers of high-risk AI systems shall conduct a conformity assessment before placing the system on the market" is decomposed into its component semantic nodes — the role (Provider), the AI system type (High-risk), the obligation type (ConformityAssessment), the timing condition (BeforePlacingOnMarket) — and stored as a subgraph. Reasoning over this layer allows the platform to answer questions like "which of my obligations have an upcoming deadline?" by traversing DeadlineNode connections.
Entity Binding Layer
This layer connects regulatory obligations to the customer's specific AI system profile: AISystemNode, DeploymentContextNode, DataProcessingNode, HumanOversightNode, TechnicalDocumentationNode. When a customer registers their AI system in TraceGov.ai, the platform creates an entity binding that maps their system's properties to the regulatory obligation graph. The TAMR+ reasoning then traverses the combined customer + regulatory graph to identify which obligations apply, which are satisfied, and which have gaps.
Graph Scale (TraceGov.ai Production Knowledge Graph)
31
OWL entity types
47K+
regulatory nodes
180K+
obligation relations
4. Evaluation Status: The Version 2.7 Correction
Earlier versions of the TAMR+ working paper reported benchmark scores, a tier-level breakdown and comparisons with other retrieval methods. Version 2.7, in preparation, withdraws those figures because no source file was found for them (doi.org/10.5281/zenodo.18929634). This article therefore reports no benchmark result for TAMR+; a new evaluation run with retained artefacts is planned.
TRACE, the paper's answer score, is a five-dimension score from 0 to 1, not an accuracy rate.
5. Cost at Retrieval Time
TAMR+ makes no LLM calls during retrieval. The cost difference comes from where the LLM is used: TAMR+ retrieves the relevant obligation subgraph with graph operations and keeps LLM calls for the final synthesis step, rather than feeding the full regulation into a large context window for every query.
6. The TRACE Score: 0–100 Compliance Readiness Metric
The TRACE score — Traceability, Regulatory Coverage, Assessment Completeness, and Evidence quality — is a 0–100 readiness metric derived from graph traversal across an organization's AI system profile against the full EU AI Act obligation network. It provides compliance teams with a single number that quantifies their current compliance posture and enables progress tracking over time.
The score is computed across four weighted dimensions:
Traceability (25 points)
Measures the completeness of your AI system's documentation provenance — training data lineage, model versioning, deployment records, and human oversight logs. A score of 25 means complete provenance documentation across all registered AI systems.
Regulatory Coverage (25 points)
Measures how many of the applicable EU AI Act obligations for your risk tier have been addressed in your documentation and processes. A high-risk system with partial documentation scores proportionally lower on this dimension.
Assessment Completeness (25 points)
Measures the completeness of required conformity assessment procedures — fundamental rights impact assessments, post-market monitoring plans, and incident reporting procedures — relative to the obligations applicable to your AI systems.
Evidence Quality (25 points)
Measures the quality and verifiability of the evidence supporting your compliance claims — not just whether documentation exists, but whether it would withstand scrutiny from a national market surveillance authority.
The TRACE score is updated automatically as documentation is submitted, gap items are closed, and monitoring data is received. Teams can track their score trajectory over time, set target scores by compliance deadline, and receive automated alerts when a score drops due to a regulatory update that adds new requirements to their obligation profile.
7. Six Platform Modules: End-to-End Compliance Lifecycle
TraceGov.ai organizes the EU AI Act compliance lifecycle into six sequential modules. Each module is independently deployable — organizations can start with Classification if they are in early compliance assessment, or start with Monitoring if they have existing documentation that needs ongoing verification — but the full platform delivers the greatest value as an integrated compliance program.
Classification Module
Determines the risk tier of each AI system — prohibited, high-risk (Annex III or IV), limited-risk, or minimal-risk — through TAMR+ graph traversal against the full classification criteria. Produces a classification report with the regulatory path that justifies the tier determination and flags any classification ambiguities requiring human legal review.
Gap Analysis Module
Maps every applicable obligation for the classified AI system against the organization's current documentation and process state, producing a structured gap register with obligation reference, gap description, remediation priority, and estimated effort to close. Updated automatically when regulatory guidance changes.
Documentation Module
Generates structured technical documentation templates pre-populated with the organization's AI system profile data, covering Article 11 and Annex IV requirements. Templates are generated from the obligation graph, ensuring that all required documentation elements are present and correctly cross-referenced.
Conformity Assessment Module
Guides organizations through the conformity assessment procedure required before placing a high-risk AI system on the market, including self-assessment checklists, notified body engagement support, and CE marking preparation workflows for systems requiring third-party assessment under Article 43.
Registration Module
Manages registration in the EU AI Act database (Article 71) — generating the required registration data package, tracking registration status, and managing updates when the AI system or its deployment context changes. Integrates with the EU database API where available.
Monitoring Module
Implements the post-market monitoring requirements of Articles 72 and 73 — automated incident detection, performance drift alerting, and periodic compliance review scheduling. The TRACE score is updated continuously from monitoring data, providing a real-time compliance health signal.
8. Integrations: REST API, Zapier, SAP GRC, ServiceNow
TraceGov.ai is designed to integrate into existing enterprise compliance and governance infrastructure rather than requiring organizations to adopt a new standalone system. The platform exposes its TAMR+ reasoning capabilities through a REST API and supports four primary integration patterns:
REST API
Full programmatic access to all six compliance modules. Supports batch processing for portfolio-level compliance assessments — submit 50 AI system profiles, receive 50 classification reports and gap analyses. OpenAPI 3.0 specification provided. Rate limits: 1,000 queries/hour on standard plan, 10,000/hour on enterprise.
Zapier Integration
No-code automation for compliance workflow triggers. Pre-built Zaps connect TraceGov.ai compliance events — gap identified, TRACE score threshold breached, regulation updated — to actions in Slack, Jira, Asana, Notion, and email. Enables compliance monitoring without engineering resources.
SAP GRC Connector
Bidirectional sync between TraceGov.ai AI system profiles and SAP GRC risk registers. Compliance gaps surface as SAP GRC controls deficiencies; TRACE score changes trigger SAP GRC risk reviews. Designed for enterprises using SAP GRC as their primary governance framework who need EU AI Act coverage without migrating to a new system.
ServiceNow Module
Native ServiceNow module that surfaces TraceGov.ai compliance findings in the ServiceNow GRC and ITSM interfaces. Compliance gaps become ServiceNow tasks; TRACE score is surfaced in GRC dashboards; regulatory update alerts create change management tickets. Available on ServiceNow Store.
For organizations building custom compliance infrastructure, the REST API supports webhook-based event delivery for real-time compliance event streaming. Integration documentation, Postman collections, and reference implementations are available in the TraceGov.ai developer portal.
9. Pricing: Compliance-as-a-Service Model
TraceGov.ai is priced on a compliance-as-a-service model based on the number of AI systems under management and the compliance modules activated. This aligns platform costs with the scale of the compliance program rather than with query volume, which would create perverse incentives against thorough compliance analysis.
Starter — Up to 5 AI systems
Includes Classification and Gap Analysis modules. Unlimited TAMR+ queries against your registered AI systems. TRACE score dashboard. REST API access (1,000 queries/hour). Monthly regulatory update digest.
Contact for pricing →
Professional — Up to 25 AI systems
All six compliance modules. TRACE score with module-level breakdown. SAP GRC or ServiceNow integration (one connector). Quarterly compliance review session with Quantamix advisory team. Priority regulatory update notifications (<72 hours).
Contact for pricing →
Enterprise — Unlimited AI systems
All modules plus custom OWL entity types for industry-specific regulations. All integrations including Zapier and REST API (10,000 queries/hour). Dedicated compliance success manager. Custom TAMR+ tuning for your regulatory jurisdiction. On-premise deployment option for air-gapped environments.
Contact for pricing →
10. Frequently Asked Questions
What is the TAMR+ methodology used in TraceGov.ai?▾
What does the TAMR+ paper report on evaluation?▾
What is the TRACE score?▾
Which EU AI Act obligations does TraceGov.ai cover?▾
Related EU AI Act Compliance Guides
How to Comply with the EU AI Act
Step-by-step guide to EU AI Act compliance obligations, timelines, and documentation requirements
EU AI Act Conformity Assessment
What conformity assessment requires, when third-party assessment is mandatory, and how to prepare
EU AI Act Compliance Guide
The comprehensive pillar guide to EU AI Act compliance for European enterprises
AI Governance in Europe
The broader EU AI governance landscape and how compliance fits within enterprise AI governance