Chapter III · High-risk AI systems
Article 12 — Record-keeping
Official text
Each paragraph records where its wording comes from. Only text reproduced unchanged from the Official Journal is authentic; consolidated text is editorial and has no legal value. Paragraphs, subparagraphs and points each have their own link.
High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system.
Authentic — as published in the Official Journal
In order to ensure a level of traceability of the functioning of a high-risk AI system that is appropriate to the intended purpose of the system, logging capabilities shall enable the recording of events relevant for:
- (a)
identifying situations that may result in the high-risk AI system presenting a risk within the meaning of Article 79(1) or in a substantial modification;
- (b)
facilitating the post-market monitoring referred to in Article 72; and
- (c)
monitoring the operation of high-risk AI systems referred to in Article 26(5).
Authentic — as published in the Official Journal
For high-risk AI systems referred to in point 1 (a), of Annex III, the logging capabilities shall provide, at a minimum:
- (a)
recording of the period of each use of the system (start date and time and end date and time of each use);
- (b)
the reference database against which input data has been checked by the system;
- (c)
the input data for which the search has led to a match;
- (d)
the identification of the natural persons involved in the verification of the results, as referred to in Article 14(5).
Authentic — as published in the Official Journal
The formal analysis of Article 12
Article 6 is formalised first. The remaining articles follow.
Article 12 is formalised node by node: each rule as a deontic position with its operator, each exception with its rank, each predicate resolved against the definitions in Article 3.
What members get, per article
- the rule logic: every norm as a formal position, with the defeater chain that decides which exception wins
- the competency questions and their answers, every unanswered one marked as a gap and named
- the ontology: predicates bound to AISV (AI Standardisation Vocabulary) and to the definitions they depend on, exportable as JSON-LD and OWL
- the documentation: the Article 6(4) assessment record generated from a fact set, with its derivation and the version of the law it was decided against
Built for providers claiming the 6(3) derogation, for the counsel who has to defend that claim, and for the auditor who reads it afterwards.
Access is invite-only and opening in stages. Article 6 is formalised first; the remaining articles follow.
No mail client? Write to hello@signatu.com
Already a member? Sign in
Commentary in preparation
The official text above is complete. The editorial layer for this article — duties, the roles bound by them, the AISV concepts that model them, and the European standards written to support them — is in preparation, in the same form as the articles already published.
See the published articles