Private beta · access reviewed manually · no public retrieval
EU AI Act context, with the source attached.
Retrieve verified passages from Regulation (EU) 2024/1689 through one stable REST contract. CorpusMesh returns citations, version metadata, and an abstention decision. Your product keeps control of its model, prompts, and compliance workflow.
What this page claims, and where the proof is
- Passages come back with official EUR-Lex citations.
- Coverage is one official regulation, in English.
- Versions are immutable and change only after review.
- Retrieval quality is measured on a sealed fixture set.
Numbers on this page keep their dataset, version, and date. None of them is a service level.
- Published evidence version
- 2026-08-21.1
- Coverage
- Regulation (EU) 2024/1689
- Language
- English
- Official source
- EUR-Lex (opens the official source in a new tab)
Exhibit A · Reviewed public Source Trace
Article 6 and Annex III, returned together.1
This is not placeholder copy. The passages and scores below come from the reviewed internal retrieval published in the Source Trace.
How do Article 6 and Annex III work together to identify high-risk AI systems?
language: enjurisdiction: eutop_k: 10012. In addition to the high-risk AI systems referred to in paragraph 1, AI systems referred to in Annex III shall be considered to be high-risk.
- Citation
- Article 6 Classification rules for high-risk AI systems (opens the official source in a new tab)
- Document
- Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence
- Chunk
- chk_34924b790ce0a55d5f8bf88a25536329cc1c41c6
- Chunk sha256
- eeed91ee4bc5...
021. Irrespective of whether an AI system is placed on the market or put into service independently of the products referred to in points (a) and (b), that AI system shall be considered to be high-risk where both of the following conditions are fulfilled: (a) the AI system is intended to be used as a safety component of a product, or the AI system is itself a product, covered by the Union harmonisation legislation listed in Annex I; (b) the product whose safety component pursuant to point (a) is the AI system, or the AI system itself as a product, is required to undergo a third-party conformity assessment, with a view to the placing on the market or the putting into service of that product pursuant to the Union harmonisation legislation listed in Annex I.
- Citation
- Article 6 Classification rules for high-risk AI systems (opens the official source in a new tab)
- Document
- Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence
- Chunk
- chk_1540328c15af4cca9c3b160011a627f593d4c3ed
- Chunk sha256
- 00b56a3a4b45...
03High-risk AI systems pursuant to Article 6(2) are the AI systems listed in any of the following areas:
- Document
- Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence
- Chunk
- chk_3b49a61004f9e4235bffaf8a52b96cdaabe61128
- Chunk sha256
- 5240ae49a099...
04High-risk AI systems referred to in Article 6(2)
- Document
- Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence
- Chunk
- chk_ed0442ab09b93b6d7eefc3e19981922237d63df5
- Chunk sha256
- dd83054cc9f5...
053. By derogation from paragraph 2, an AI system referred to in Annex III shall not be considered to be high-risk where it does not pose a significant risk of harm to the health, safety or fundamental rights of natural persons, including by not materially influencing the outcome of decision making. The first subparagraph shall apply where any of the following conditions is fulfilled: (a) the AI system is intended to perform a narrow procedural task; (b) the AI system is intended to improve the result of a previously completed human activity; (c) the AI system is intended to detect decision-making patterns or deviations from prior decision-making patterns and is not meant to replace or influence the previously completed human assessment, without proper human review; or (d) the AI system is i...
- Citation
- Article 6 Classification rules for high-risk AI systems (opens the official source in a new tab)
- Document
- Regulation (EU) 2024/1689 laying down harmonised rules on artificial intelligence
- Chunk
- chk_7dbde2a0f741a2bcae87753547ec6f3b7592d3d9
- Chunk sha256
- f859f5a2e435...
Exhibit B · Coverage perimeter
One official regulation. No implied legal coverage.2
The current beta is intentionally narrow. Every addition must pass its own source, rights, canonicalization, and retrieval review.
In scope · The verified English text
- English EU AI Act from EUR-Lex, with the approved source set and version pinned in the issued private-beta entitlement
- Source identity, official article and annex anchors, immutable version, and lineage checksums
- Additional regulations and implementation instruments require a separately verified version and explicit approval before inclusion in the customer entitlement
Out of scope · Anything outside the source boundary
- Legal advice or compliance decisions
- Draft guidance, case law, national implementation material, and copyrighted standards text
- Other languages, jurisdictions, or unverified commentary
- Volatile signatory lists and documents without final official publication status
- Jurisdictions
- European Union
- Languages
- English
- Source types
- EU legislation, Official guidance, Codes and mandatory templates
The published trace covers the English base Regulation (EU) 2024/1689 at version 2026-08-21.1. The nine-document internal version also includes the amending Regulation and approved official implementation instruments; customer scope is agreed and verified before access. National implementation, case law, standards text, and unofficial commentary remain outside scope.
Exhibit C · Versions and updates
A source change does not silently rewrite the corpus.3
During an approved beta, CorpusMesh checks the official source set daily. A detected change creates a new immutable candidate version. It becomes retrievable only after source review, canonicalization checks, corpus-specific evaluation, and rollback preparation.
No public update SLA applies. Beta entitlements begin pinned to version 2026-08-21.1 and move only after the new version is verified and the customer is notified.
2026-08-24.39 canonical documents, 16 manifestations, 2,298 chunks. Passed a 105-fixture protected replay with 0 boundary violations. Not yet the public evidence version.
Active internally2026-08-21.1English base Regulation (EU) 2024/1689. The reviewed public benchmark and Source Trace remain pinned to this version.
Published evidence
- 01Detect
Compare the approved official source against its sealed snapshot.
- 02Review
Verify the source change, rights boundary, structure, metadata, and lineage.
- 03Evaluate
Rebuild the candidate and run the corpus-specific retrieval fixtures.
- 04Activate
Switch versions only with a tested rollback path and customer notice.
Exhibit D · Evaluation
Measured on one sealed fixture set, not promised everywhere.4
These values come from 80 responses recorded against the deployed private-beta endpoint on 2026-08-21. They describe this corpus, version, and fixture set only.
Recall@10
96.2%
Required evidence found in the first ten passages.
Source-anchor recall@10
98.3%
Expected official article or annex anchor present.
nDCG@10
0.820
Ordering quality, with credit for relevant passages near the top.
Abstention accuracy
100%
Unsupported queries returned an explicit abstention.
Citation precision@10
53.4%
Share of passages matching a required anchor. Measures focus, not factual correctness.
Boundary violations
0
Results outside the enforced language and jurisdiction scope.
EU AI Act API contract
Filter the request. Keep the citation boundary in the response.
The private-beta contract returns retrieval context for your application. It does not classify a system or decide whether it complies with the Act.
POST /v1/retrieve · documented request shape
{
"knowledge_base": "eu-ai-act-reference",
"query": "How do Article 6 and Annex III work together to identify high-risk AI systems?",
"filters": {
"language": [
"en"
],
"jurisdiction": [
"eu"
]
},
"top_k": 5,
"profile": "active"
}Filters can narrow the EU AI Act entitlement. They cannot add another jurisdiction, source set, or unverified material.
language
jurisdiction
subject
profileEach result identifies its source and scope. abstention.decision separates a supported answer boundary from unsupported evidence.
version
citation
source_anchor
source_snapshot_id
language
jurisdictionMore than raw legal text. Less than a compliance decision.
CorpusMesh maintains retrieval evidence between the official source and the product workflow you control.
| Capability | Raw legal text | CorpusMesh EU AI Act API | Compliance checker |
|---|---|---|---|
| Official text access | Yes | Yes, from the approved EUR-Lex source | Varies by product |
| Versioned retrieval | No retrieval layer | Immutable corpus version and retrieval profile | Not the product boundary |
| Passage citations | Document links | Ranked passages, anchors, source identity, and checksums | May cite guidance or controls |
| Compliance decision | No | No | May support an assessment workflow |
| Customer model | Customer builds everything | Customer keeps its model, prompts, and interface | Often part of a broader platform |
Built for product workflows
Context for the system you already own.
CorpusMesh does not make the legal or compliance decision. It gives your workflow inspectable source material.
AI product teams
Ground assistants and product features in the current verified regulation without maintaining the source pipeline in-house.
RegTech teams
Link control mappings, evidence workflows, and change reviews back to official articles and annexes.
Governance teams
Retrieve passages with explicit jurisdiction, language, version, authority, and citation boundaries.
Private beta · Private beta · manual approval
Does your product need maintained EU AI Act context?
Tell us the application, source obligations, filters, and expected request volume. Access is reviewed manually.
- What the status means
- Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
- Access boundary
- Private-beta access is approved against one application, its source set, version, service boundary, and final access contract. Any change to the approved source set or version requires verification, explicit scope approval, and customer notice.
Provenance notes
- Reviewed public Source TraceOpen the Source Trace
- Trace
- ret_65f7825943714f31a57851d4eb8502e9
- Reviewed
- 2026-08-21 by CorpusMesh product and source review
- Official source verified
- 2026-08-21
- Trace checksum
- sha256 88821ad972ee...
- Official sourceEUR-Lex text (opens in a new tab)
- Document
- CELEX:32024R1689
- Publisher
- EUR-Lex, Publications Office of the European Union
- Reuse
- EUR-Lex legal documents permit commercial reuse unless a document states otherwise. Every additional source still requires its own rights review.
- Internal version record
- Version
- 2026-08-24.3
- Verified
- 2026-08-24
- Contents
- 9 canonical documents · 16 manifestations · 2,298 chunks
- Replay
- 105 protected fixtures · 0 boundary violations
- Publication
- Summary only. The internal replay is not published.
- RAG evaluation, deployed endpointRead the RAG evaluation
- Fixtures
- 80 fixed queries (50 calibration, 30 validation)
- Corpus
- 1,160 rows · gemini-embedding-2 768D
- Recorded
- 2026-08-21
- Deployed commit
- 57c28e3
- Fixture set
- sha256 c1780012a679...