Skip to content

Add: Guidelines on the Scope of Obligations for GPAI Providers#17

Merged
carloshvp merged 2 commits into
GenAI-Gurus:mainfrom
2digitsleft:add-guidelines-gpai-scope
May 11, 2026
Merged

Add: Guidelines on the Scope of Obligations for GPAI Providers#17
carloshvp merged 2 commits into
GenAI-Gurus:mainfrom
2digitsleft:add-guidelines-gpai-scope

Conversation

@2digitsleft
Copy link
Copy Markdown
Contributor

Adds the European Commission's Guidelines on the Scope of Obligations for Providers of GPAI Models to the "European Commission" subsection under "Official EU Sources".

What it is: The Commission's guidelines (18 July 2025) clarifying who counts as a GPAI provider under Articles 53–55. Covers: the 10²³ FLOP threshold for GPAI classification and 10²⁵ FLOP threshold for systemic risk, the rules for downstream providers who fine-tune or modify a GPAI model, lifecycle obligations from pre-training onward, open-source exemptions, and the relationship between GPAI models and AI systems built on them.

Why it belongs: GPAI obligations entered into application on 2 August 2025. These Guidelines are the Commission's primary interpretive document on Articles 53–55 and complement both the GPAI Code of Practice (PR #1, if merged) and the Training Content Template. They're the authoritative answer to "does my model count as GPAI?" and "what happens when I fine-tune one?".

Checklist:

  • Directly relevant to EU AI Act compliance
  • Publicly accessible
  • Working link
  • Not already listed
  • Description under 100 characters
  • Hyphen separator

@carloshvp
Copy link
Copy Markdown
Member

Thanks for the contribution @2digitsleft. The GPAI provider scope guidelines are directly relevant and nicely placed with the Commission sources. I’m merging this now.

@carloshvp carloshvp merged commit 562780a into GenAI-Gurus:main May 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants