Coverage matrix and justification for standards and specifications
Per requirement of Section 2: the harmonised standard or common specification applied with its version, the publication status of the reference in the Official Journal, what the standard or specification does and does not cover, and on departure the Article 41(5) justification with the technical solution chosen and the test showing equivalence.
The official source remains authoritative. This is general information about obligations and not legal advice. See this object on the map
Address and citation
This object has an address of its own that is never renamed or reused. Store the identifier in your own file, not the title or the link.
- Identifier
praxikon:eu:ai-act:evidence:standards-conformity-justification-file- Payload hash (sha256)
509b7a86a787c973d0cc794e078db8ee608a13d2331d6927de09686dafe11e0d
Citation line
Praxikon, "Coverage matrix and justification for standards and specifications", praxikon:eu:ai-act:evidence:standards-conformity-justification-file@1.0.0, dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0 (schema 1.5.0), effective_at 2026-08-08T00:00:00.000Z, known_at 2026-09-06T00:00:00.000Z, sha256 509b7a86a787c973d0cc794e078db8ee608a13d2331d6927de09686dafe11e0d- Version
- 1.0.0
- Legal time (effective_at)
- 2 August 2026
- Knowledge time (known_at)
- 6 September 2026
- Closed on
- Not closed
- Topics
- conformity, evidence, standards
Review status: Editorially reviewed (6 September 2026). Next check due by 5 March 2027. The check date is the knowledge date of this version; no later recheck has been recorded.
What this object links to
Every relation appears below as a path: from the source with its locator, through the conditions and exceptions of the object carrying the relation, to the consequence. A locator belongs to a statement in the data and not to a relation, so the source is the source anchor of the carrying object.
The obligation this hangs off
1 of 1 shown
The object belongs to this obligation. The source line it hangs off sits there.
Source
This object carries no official fact of its own. The source line below sits on the obligation it hangs off; the link itself is recorded editorially.
Digital Omnibus on AI 2026/1744
Locator: Article 1, points (17) and (18), amending Article 40(2) and Article 42
praxikon:eu:ai-act:source:reg-eu-2026-1744
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 40(1) to (3)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 41(1) to (3)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 41(4), (5) and (6)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 42(1) and (2)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official source
Via
No condition or exception recorded on this object.
Consequence
ObligationArticles 40 to 42: standards, common specifications and presumption of conformity
praxikon:eu:ai-act:obligation:article-40-42-standards-and-specifications
What this object is about
2 of 2 shown
The object is about this role. Undifferentiated: it does not follow that the duty rests on this role.
Source
This object carries no official fact of its own. The source line below sits on the obligation it hangs off; the link itself is recorded editorially.
Digital Omnibus on AI 2026/1744
Locator: Article 1, points (17) and (18), amending Article 40(2) and Article 42
praxikon:eu:ai-act:source:reg-eu-2026-1744
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 40(1) to (3)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 41(1) to (3)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 41(4), (5) and (6)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 42(1) and (2)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official source
Via
No condition or exception recorded on this object.
Consequence
praxikon:eu:ai-act:actor:gpai-model-provider
praxikon:eu:ai-act:actor:provider
What points at this object
Where this evidence comes from
1 of 1 shown
This is what has to be in the file to show that the action was carried out.
Source
Official fact on this object, with its locator.
Digital Omnibus on AI 2026/1744
Locator: Article 1, points (17) and (18), amending Article 40(2) and Article 42
praxikon:eu:ai-act:source:reg-eu-2026-1744
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 40(1) to (3)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 41(1) to (3)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 41(4), (5) and (6)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official sourceEU Artificial Intelligence Act 2024/1689
Locator: Article 42(1) and (2)
praxikon:eu:ai-act:source:reg-eu-2024-1689
Open official source
Via
- Condition | allThe presumption in Article 40(1) arises only where the references of the harmonised standard have been published in the Official Journal of the European Union in accordance with Regulation (EU) No 1025/2012, and it reaches only to the extent that those standards cover those requirements or obligations. The same holds for the cybersecurity certification of Article 42(2), the references of which must likewise have been published in the Official Journal.
- Condition | allThe justification duty of Article 41(5) arises only where a common specification has actually been established by implementing act for the requirement concerned and the provider does not apply it. Where no such specification exists, there is nothing to depart from and you demonstrate conformity by the ordinary route.
- ExceptionA presumption of conformity is not a finding of compliance. The text says the system shall be presumed to be in conformity, and only in so far as the standard or the specification covers the requirements or obligations concerned. Outside that coverage the burden of proof rests fully on the provider, and a market surveillance authority can rebut the presumption where the system in fact does not meet the requirements.
- ExceptionArticle 41(4) makes a common specification lapse as soon as the standard exists: when reference to a harmonised standard is published in the Official Journal of the European Union, the Commission repeals the implementing acts, or parts thereof, which cover the same requirements or obligations. A file leaning on a repealed specification thereby loses its basis.
As long as this exception is not ruled out, the outcome stays conditional and you have to establish it yourself.
Relation recorded on: Articles 40 to 42: standards, common specifications and presumption of conformity
Consequence
ObligationArticles 40 to 42: standards, common specifications and presumption of conformity
praxikon:eu:ai-act:obligation:article-40-42-standards-and-specifications
When this applies
No condition recorded on this object.
When this does not apply
No exception recorded on this object.
Referring to this object
Citation block
Copy this reference into your advice, article or file. The identifier, the version and the hash keep the statement findable later, even once the dataset has moved on.
Reference
Praxikon, "Coverage matrix and justification for standards and specifications", praxikon:eu:ai-act:evidence:standards-conformity-justification-file@1.0.0, dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0 (schema 1.5.0), effective_at 2026-08-02T00:00:00.000Z, known_at 2026-09-06T00:00:00.000Z, sha256 509b7a86a787c973d0cc794e078db8ee608a13d2331d6927de09686dafe11e0d, https://www.praxikon.com/en/verkenner/evidence/standards-conformity-justification-file (https://www.praxikon.com/api/v1/entities?id=praxikon%3Aeu%3Aai-act%3Aevidence%3Astandards-conformity-justification-file&effective_at=2026-08-02&known_at=2026-09-06&lang=en, accessed 2026-09-21)
Short form
praxikon:eu:ai-act:evidence:standards-conformity-justification-file@1.0.0 (sha256 509b7a86)
BibTeX
@misc{praxikon-eu-ai-act-evidence-standards-conformity-justification-file-1-0-0,
author = {{Praxikon}},
title = {Coverage matrix and justification for standards and specifications},
year = {2026},
version = {1.0.0},
number = {praxikon:eu:ai-act:evidence:standards-conformity-justification-file},
howpublished = {AI Act Change \& Evidence Graph, dataset 2.2.0, schema 1.5.0},
note = {effective_at 2026-08-02T00:00:00.000Z; known_at 2026-09-06T00:00:00.000Z; sha256 509b7a86a787c973d0cc794e078db8ee608a13d2331d6927de09686dafe11e0d},
url = {https://www.praxikon.com/en/verkenner/evidence/standards-conformity-justification-file},
urldate = {2026-09-21},
language = {en}
}CSL JSON
[
{
"id": "praxikon:eu:ai-act:evidence:standards-conformity-justification-file@1.0.0",
"type": "dataset",
"title": "Coverage matrix and justification for standards and specifications",
"container-title": "AI Act Change & Evidence Graph",
"publisher": "Praxikon",
"version": "1.0.0",
"number": "praxikon:eu:ai-act:evidence:standards-conformity-justification-file",
"URL": "https://www.praxikon.com/en/verkenner/evidence/standards-conformity-justification-file",
"language": "en",
"issued": {
"date-parts": [
[
2026,
9,
6
]
]
},
"accessed": {
"date-parts": [
[
2026,
9,
21
]
]
},
"note": "dataset praxikon:sys:registry:dataset:ai-act-implementation-graph 2.2.0; schema 1.5.0; effective_at 2026-08-02T00:00:00.000Z; known_at 2026-09-06T00:00:00.000Z; sha256 509b7a86a787c973d0cc794e078db8ee608a13d2331d6927de09686dafe11e0d; retrieved_from https://www.praxikon.com/api/v1/entities?id=praxikon%3Aeu%3Aai-act%3Aevidence%3Astandards-conformity-justification-file&effective_at=2026-08-02&known_at=2026-09-06&lang=en; licence https://www.praxikon.com/nl/legal/terms"
}
]How to verify a reference later is set out in the methodology. Terms
For agents and integrations
This page and the machine output come from the same object and the same two time axes.