Rule set sha256:8425ad0448a8

rego-gpai-53b-001

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

rules/rego/complyedge/gpai/downstream_obligations.rego

Citation
Regulation (EU) 2024/1689, Article 53(1)(b)
Condition
Providers of general-purpose AI models shall draw up, keep up-to-date and make available information and documentation to providers of AI systems who intend to integrate the general-purpose AI model into their AI systems. The information shall enable downstream providers to understand the capabilities and limitations of the GPAI model and to comply with their obligations under this Regulation; it shall contain, at a minimum, the elements set out in Annex XII.
Layer 1 detects
"downstream", then the word "no", "not", "without" or "lack" (any ending), then documentation, information or support; the word "no", "not", "without" or "lack" (any ending), then "downstream", then provider or integrator, then doc, info or guid; "gpai" or "foundation model" (space, hyphen or one word), then the word "no", "not" or "without", then "downstream", then obligat or support; "api" or "model", then the word "no", "not" or "without", then "integration guid" or "usage doc" (space, hyphen or one word), then "downstream"; and provid or distribut, then model, then the word "no", "not" or "without", then "downstream" or "integrator", then doc, guid or info. Case is ignored, the parts must sit on one line in the order given with any words between them, and a part not called a word can start inside a longer word. It matches wording, not meaning: it misses the practice told without these words ("Ship the model weights to integrators with nothing explaining what it can and cannot do." does not fire), and it fires on a denial ("Downstream
Condition type
deterministic
Status in the file
approved