Rule set sha256:a7e715b79299
EU_AI_ACT_ART12_RECORD_KEEPING_001
One rule of the rule set with digest a7e715b792994b004a7cc9714100077fad036164172ce42812ed396af0b727f5. An audit record that names this digest and this rule was decided by the rule as shown here. Every rule in this set.
| Rule | EU_AI_ACT_ART12_RECORD_KEEPING_001 |
|---|---|
| Rule version | 5fe3eced0f7a3cb60e7b8f7f032ed0da11642e01b13514ecc29804c82e6d0490 |
| Provision | Regulation (EU) 2024/1689, Article 12 ELI: http://data.europa.eu/eli/reg/2024/1689/art_12/oj |
| Approval | Approved Approved by Leo Celis (via agent review per §5.1 amendment v1.1) on 2026-10-22 |
rules/regulations/eu/eu_ai_act_article12_record_keeping.yaml
- Citation
- Regulation (EU) 2024/1689, Article 12 (Record-keeping): 1. High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system. 2. 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). 3. 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).
- Condition
- Requires high-risk AI systems to technically allow for the automatic recording of events (logs) over the lifetime of the system, with logging capabilities enabling traceability appropriate to the intended purpose. Article 12.
- Layer 1 detects
- "no", "without", "disable" (and longer forms such as "disabled"), "bypass", "skip", "skipping" or "turn off", followed by "logging", "logs", "event log", "audit log" or "record keeping" (also "record-keeping" or "recordkeeping"), then "for", "on" or "in", then "high-risk AI", "AI system" or "biometric"; "high-risk AI" or "AI system" (singular) followed by "without" or "lacking", optionally "automatic", and then "logging", "logs", "event recording" or "traceability"; "Article 12", "Art 12", "Art. 12" or "record keeping" followed by "obligation" or "requirement" and then "not met", "ignored", "skipped" or "bypass" (and longer forms); "traceability" or "audit trail" followed by "not provided", "not implemented", "not enabled", "disabled" or "removed"; and "deploy", "operate" or "run" (and longer forms) followed by "high-risk AI" or "biometric system", then "without" or "lacking", then "logs", "logging", "traceability" or "audit trail". "High-risk" may also be written "high risk". Case is ignored, the words must follow each other with no other word between them unless stated, and a phrase can start inside a longer word. It matches wording, not meaning: it misses the practice told in other words, it does not check that the system is high-risk (any "AI system" counts), and it fires on text that only names the practice, such as a refusal. Whether a text does the practice is judged in Layer 2.
- Condition type
- regex; semantic condition in the file, not run by the engine
- Status in the file
- approved