Rule set sha256:c63def17fac2

EU_AI_ACT_GPAI_TECHNICAL_DOCUMENTATION_001

One rule of the rule set with digest c63def17fac2df12ab70941d8fcb7678e9a670479ea0d6dce87e7ddd4dc96079. An audit record that names this digest and this rule was decided by the rule as shown here. Every rule in this set.

RuleEU_AI_ACT_GPAI_TECHNICAL_DOCUMENTATION_001
Rule versioned08bf40ac241dc2581b6222c37167a04ddda588988123353065a6c910377712
ProvisionRegulation (EU) 2024/1689, Article 53(1)(a)
ELI: http://data.europa.eu/eli/reg/2024/1689/art_53/par_1/pnt_a/oj
ApprovalApproved
Approved by Leo Celis (via agent review per §5.1 amendment v1.1) on 2026-10-22

rules/regulations/eu/eu_ai_act_gpai_technical_documentation.yaml

Citation
Regulation (EU) 2024/1689, Article 53(1)(a): draw up and keep up-to-date the technical documentation of the model, including its training and testing process and the results of its evaluation, which shall contain, at a minimum, the information set out in Annex XI for the purpose of providing it, upon request, to the AI Office and the national competent authorities;
Condition
Requires providers of general-purpose AI models to draw up and keep up-to-date technical documentation of the model, including training and testing processes and evaluation results, and to make it available to the AI Office and national competent authorities on request. Article 53(1)(a) mandates technical documentation per Annex XI.
Layer 1 detects
deploy, release, distribute, ship or launch, in any form, optionally "a" or "the", then GPAI, general-purpose AI, foundation model, large language model or LLM, then without, lacking, missing or no, then documentation, model card, technical documentation, technical docs or data sheet ("ship the foundation model missing technical documentation"); and, as a second sequence, "no" or "without" as words of their own, then "Annex XI" or "technical documentation", then "for" or "of", then GPAI, general-purpose AI or foundation model ("without technical documentation for the GPAI" does not match, "the" is not allowed there). It matches wording, not meaning: it does not read whether Annex XI documentation exists, so it misses the practice told in other words ("We release the weights of our GPAI model on Friday; the Annex XI file is not written yet."), 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