Skip to content
EU AI Act · EU-AI-ACT-ART-54-GPAI-CODES-OF-PRACTICE

EU AI Act Articles 53(4), 55(2) and 56 - GPAI means of demonstrating compliance

Document the selected route for demonstrating GPAI compliance; code adherence is optional and alternative adequate means require Commission assessment

MEDIUMProcess dutyGovernanceBinding regulationIn forceEnforceable from 2 August 2025

Where this comes from

Provision: Articles 53(4), 55(2) and 56 - GPAI means of demonstrating compliance

Instrument: EU Artificial Intelligence Act (Regulation (EU) 2024/1689)

Citation: Articles 53(4), 55(2) and 56, Regulation (EU) 2024/1689

Text version: Regulation (EU) 2024/1689, consolidated 27 July 2026; original OJ L 12 July 2024 and amendment (EU) 2026/1744

Checked against the source: 6 September 2026

Read the official text ↗

Who it applies to

GPAI model provider in scope (Art. 2, Art. 3(63)) — all of these:

  • Project involves providing a general-purpose AI model (GPAI)
  • GPAI assessed Union model scope: YES

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Record the relevant approved code or harmonised standard, its exact version, coverage and adherence evidence
  • Where neither route is used, preserve alternative adequate means of compliance for Commission assessment
  • Assess each underlying Article 53 or 55 duty separately; signing a code is not proof of full conformity
  • Record the model-provider scope, relevant model version and Article 111(3) placement-date transition before an enforcement conclusion
  • Choosing alternative adequate means does not become a mandatory code-adherence failure

Evidence an auditor expects

  • Process recordDocument review

    GPAI compliance-route record (Articles 53(4), 55(2), 56)

    Identify the approved code or harmonised standard and its version, applicable duties and coverage evidence. Where neither is used, preserve the alternative adequate means submitted for Commission assessment. Code adherence is optional; the route does not erase the underlying duties.

Questions people ask

Does EU AI Act Articles 53(4), 55(2) and 56 - GPAI means of demonstrating compliance apply to my service?
It applies when Project involves providing a general-purpose AI model (GPAI); GPAI assessed Union model scope: YES.
When does this become enforceable?
EU AI Act Articles 53(4), 55(2) and 56 - GPAI means of demonstrating compliance is enforceable from 2 August 2025. Its current status is: in force.
What evidence does an auditor expect?
GPAI compliance-route record (Articles 53(4), 55(2), 56).

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations