Markdown Editor

GPAI Model Technical Documentation Template (EU AI Act Annex XI and XII)

Document a general-purpose AI model per EU AI Act Article 53, Annexes XI and XII, copyright policy and systemic risk

AI 与数据完整Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744, Article 53 and Annexes XI and XIIgpaimodeldocumentationmath

使用方法: Use it if you provide a general-purpose AI model in the EU. Settle the systemic-risk status and open-source exemption in section 1, then fill Annex XI for authorities and Annex XII for downstream providers. The main pitfall is giving integrators too little to meet their own obligations, or forgetting the public training content summary.

预览

GPAI Model Technical Documentation: [Model name] [version]

Technical documentation for a general-purpose AI (GPAI) model, organised on Article 53 of the EU Artificial Intelligence Act (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744, the Digital Omnibus on AI) and its Annex XI (documentation kept for the AI Office and national authorities) and Annex XII (information for downstream providers that integrate the model). It also covers the copyright policy, the public summary of training content and, where the model has systemic risk, the additional Annex XI Section 2 information. Replace every [bracketed] value and every row marked Example. The GPAI provider obligations have applied since 2 August 2025; check the consolidated text for transitional rules and later amendments. This is a documentation format, not legal advice.

Document control

FieldValue
Document ID[GPAI-DOC-001]
Provider[Legal name, address, EU authorised representative if established outside the EU]
Model name and version[Name] [version]
Model identifiers[Checkpoint hash, model ID in API]
Systemic risk status[Not systemic risk / Presumed systemic risk (training compute above 10^25 FLOP) / Designated by the Commission]
Version of this document[0.1]
Status[Draft / In review / Approved / Superseded]
Owner[@model-governance-lead]
Contributors[@research-lead], [@data-lead], [@legal], [@safety-lead]
Confidentiality[Part A: confidential, for authorities; Part B: shared under NDA with downstream providers]
Last updatedYYYY-MM-DD

Approvals

RoleNameDecisionDate
Model owner[@name][Approve / Reject]YYYY-MM-DD
Legal / regulatory[@name][Decision]YYYY-MM-DD
Safety lead (systemic risk models)[@name][Decision]YYYY-MM-DD

Revision history

VersionDateAuthorChange summary
0.1YYYY-MM-DD[@name]First draft
1.0YYYY-MM-DD[@name]Example: Documentation for release v2.0
1.1YYYY-MM-DD[@name]Example: Added evaluation results for fine-tuned v2.1

Contents

1. Scope and regulatory position

1.1 Model classification

[Explain why the model is a general-purpose AI model: generality and the range of distinct tasks it performs.] Example: A 34-billion-parameter decoder-only language model, trained by self-supervision on text and code, offered through an API and as downloadable weights for many downstream applications.

1.2 Systemic risk

QuestionAnswerEvidence
Cumulative training computeExample: 3.1 × 10^24 FLOPSection 5
Above the presumption threshold in Article 51(2)?[Yes / No]
Designated by the Commission?[Yes / No]
Notification to the Commission made (Article 52)[Yes, YYYY-MM-DD / Not applicable]

1.3 Obligations matrix

Obligation (Article 53(1))Applies?Where documented
(a) Technical documentation (Annex XI)[Yes / Exempt as open-source without systemic risk]Sections 2 to 6
(b) Information for downstream providers (Annex XII)[Yes / Exempt as above]Section 7
(c) Copyright policyYesSection 8.1
(d) Public summary of training contentYesSection 8.2
Article 55 (systemic risk)[Yes / No]Section 9
Code of Practice signatory[Yes: chapters / No: other adequate means]Section 10

2. General description of the model (Annex XI 1)

2.1 Intended tasks and types of AI systems

ItemDescription
Intended tasksExample: Text generation, summarisation, question answering, code generation, translation in 24 languages
Types of AI systems it can be integrated intoExample: Chat assistants, retrieval-augmented search, coding assistants, document processing pipelines
Not designed forExample: Autonomous control of physical systems; medical diagnosis without a validated downstream system

2.2 Acceptable use policy

[Link and summary.] Example: The acceptable use policy at [URL], version 3, prohibits use for weapons development, unlawful surveillance, generating child sexual abuse material and deceptive impersonation. API customers accept it in the terms of service; weight licensees accept it in the licence.

2.3 Release date and methods of distribution

ItemValue
Release dateYYYY-MM-DD
DistributionExample: Public API, cloud marketplaces, downloadable weights on request
RegionsExample: Worldwide including the EU

2.4 Architecture and number of parameters

ItemValue
ArchitectureExample: Decoder-only transformer, grouped-query attention, rotary position embeddings
ParametersExample: 34.2 billion (dense)
Context windowExample: 128,000 tokens
TokeniserExample: Byte-level BPE, 128,000 vocabulary

2.5 Modality and format of inputs and outputs

DirectionModalitiesFormatsLimits
InputExample: Text, imagesUTF-8 text; PNG, JPEG128k tokens; images up to 8 MP
OutputExample: TextUTF-8 text, JSON in structured mode8,192 tokens per response

2.6 Licence

[Example: API access under commercial terms; weights under the [licence name] licence, version [x], which restricts use per the acceptable use policy. Not released under a free and open-source licence.]

3. Development process and design (Annex XI 2(a) and 2(b))

3.1 Technical means for integration

[Instructions for use, infrastructure and tools needed to integrate the model into AI systems.] Example: REST API with SDKs for Python and TypeScript; self-hosting requires 2 × 80 GB GPUs at 16-bit precision or 1 × 80 GB at 8-bit; reference inference server and quantised weights provided.

3.2 Design specifications and training process

StageMethodKey choices and rationale
Pre-trainingExample: Next-token prediction on 9.5 trillion tokensData mix tuned for code and multilingual quality
Supervised fine-tuningExample: 1.2 million instruction examplesMix of licensed, synthetic and human-written data
Preference optimisationExample: Direct preference optimisation on 400,000 comparisonsChosen for stability over reinforcement learning
Safety trainingExample: Refusal and policy data, adversarial examplesTargets acceptable use policy categories

Optimisation objective and what it was meant to achieve: [Example: minimise cross-entropy in pre-training; maximise human preference for helpful and policy-compliant answers in post-training. Relevant parameters: learning rate schedule, batch size, sequence length.]

4. Training, testing and validation data (Annex XI 2(c))

Dataset categoryTypeProvenanceHow obtainedVolumeShare of tokens
Example: Public web crawlTextWeb pagesOwn crawler respecting robots.txt and machine-readable opt-outs6.1 T tokens64%
Example: Licensed contentTextNews and books publishersLicence agreements0.9 T tokens9%
Example: Public code repositoriesCodeCode hosting platformsCrawler, permissive licences only1.6 T tokens17%
Example: Synthetic dataText, codeGenerated by earlier modelsInternal pipeline0.6 T tokens6%
Example: User dataTextAPI customers who opted inOpt-in0.0 (none used)0%
Example: Human annotationInstructions, preferencesContracted annotatorsVendor contracts1.6 M examplesn/a

Curation methods: [Example: deduplication (exact and near-duplicate), language identification, quality classifier, removal of personal data patterns, filtering of sources on a blocklist of unsafe sites, removal of evaluation benchmark contamination.]

Detection of unsuitable sources and biases: [Example: source blocklists updated monthly; demographic representation analysis on a 1% sample; toxicity rates per language; documented gaps for low-resource languages.]

Testing and validation data: [Example: held-out sets drawn before training, decontaminated against training data by 13-gram overlap.]

5. Compute and energy (Annex XI 2(d) and 2(e))

ItemValueMethod
Training computeExample: 3.1 × 10^24 FLOPEstimated as 6⋅N⋅D6 \cdot N \cdot D
Training timeExample: 41 daysWall-clock
HardwareExample: 4,096 accelerators of type [x]
Energy consumptionExample: 2.9 GWhMetered at cluster level, including cooling

For a dense transformer with NN parameters trained on DD tokens, a common approximation of training compute is

C≈6 N DC \approx 6\,N\,D

Example: N=3.42×1010N = 3.42 \times 10^{10}, D=9.5×1012D = 9.5 \times 10^{12} gives C≈1.95×1024C \approx 1.95 \times 10^{24} FLOP for pre-training; post-training and failed runs counted in the total above bring it to 3.1×10243.1 \times 10^{24}.

When energy is not metered, estimate it from device-hours HH, average device power PP and data-centre power usage effectiveness:

E≈H⋅P⋅PUEE \approx H \cdot P \cdot \text{PUE}

6. Evaluation and adversarial testing

6.1 Evaluation results

AreaBenchmark or methodMetricResultNotes
Knowledge and reasoningExample: Public multi-subject benchmarkAccuracy[x]5-shot
CodingExample: Public code benchmarkpass@1[x]
MultilingualExample: Internal 24-language QA setAccuracy by language[Range]Lowest: [language]
SafetyExample: Internal harmful-request setRefusal rate on disallowed requests[x]
Over-refusalExample: Benign borderline setUnwarranted refusals[x]
BiasExample: Public bias benchmarkBias score[x]

6.2 Adversarial testing

ItemDescription
TeamsExample: Internal red team and two external organisations
ScopeExample: Jailbreaks, harmful instructions, cyber offence uplift, privacy extraction
Results summary[Summary without publishing attack details]
Mitigations applied[List]

6.3 Known limitations

[Example: hallucination of facts and citations; lower quality in low-resource languages; knowledge cut-off YYYY-MM; vulnerable to prompt injection when processing untrusted content.]

7. Information for downstream providers (Annex XII)

7.1 General description (Annex XII 1)

ItemValue
(a) Intended tasks and types of AI systems for integrationSee 2.1
(b) Acceptable use policiesSee 2.2
(c) Release date and distribution methodsSee 2.3
(d) Interaction with hardware or software not part of the modelExample: Function calling to external tools defined by the integrator; no built-in internet access
(e) Versions of relevant softwareExample: Reference inference server v1.8; tokenizer library v0.20
(f) Architecture and number of parametersSee 2.4
(g) Input and output modalities and formatsSee 2.5
(h) LicenceSee 2.6

7.2 Model elements and development (Annex XII 2)

ItemValue
(a) Technical means for integrationSee 3.1; integration guide at [URL]
(b) Modalities, formats and maximum size of inputs and outputsExample: Context window 128k tokens; maximum output 8,192 tokens; images up to 8 MP
(c) Training, testing and validation data, where applicableSummary of section 4 types, provenance and curation

7.3 Integration guidance

[Example: recommended system prompt patterns; safety settings and moderation endpoint; known failure modes; evaluation results relevant to high-risk uses; contact for downstream compliance questions.]

8. Copyright policy and training content summary

8.1 Copyright policy

ElementDescription
Policy document[Link, version, owner]
Rights reservation detectionExample: Crawler honours robots.txt and other machine-readable opt-out protocols; checks before each crawl
Lawful accessExample: No circumvention of paywalls or technical protection measures
Excluded sourcesExample: Sites listed by authorities as infringing
ComplaintsExample: Rightsholder contact point at [URL]; response within 30 days
Output measuresExample: Mitigations against reproducing protected content verbatim

8.2 Public summary of training content

ItemValue
Template used[AI Office template, version]
Publication URL[URL]
Published onYYYY-MM-DD
CoversExample: Data categories, main datasets and top domains crawled, data processing aspects

9. Systemic risk section

[Mark "Not applicable" with the reason if the model has no systemic risk.]

ItemDescription
Evaluation strategies and resultsExample: Protocols, criteria and metrics for dangerous capability evaluations (cyber, chemical and biological, autonomy); methodology for identifying limitations
Adversarial testing and model adaptationsExample: Internal and external red teaming; alignment and fine-tuning measures adopted as a result
System architecture (where applicable)Example: How safety classifiers, the model and serving components connect and feed each other
Systemic risk assessment and mitigationExample: Risk register with Union-level systemic risks and mitigations
Serious incident tracking and reportingExample: Process to report to the AI Office and national authorities without undue delay
CybersecurityExample: Weight security controls, access logging, insider risk programme

10. Maintenance, requests and contacts

ItemValue
Update triggersNew model version; new evaluation results; change of data sources; change of systemic risk status
RetentionExample: At least 10 years after the model is placed on the market
Contact for AI Office requests[Name, email]
Contact for downstream providers[Name, email, portal]
Code of Practice[Signed chapters, date / not signed: describe alternative means of compliance]
Mapping to Model Documentation Form[Link to mapping table]

Standard and licence note

Based on Regulation (EU) 2024/1689 (the Artificial Intelligence Act) as amended by Regulation (EU) 2026/1744 (Digital Omnibus on AI), Article 53 and Annexes XI and XII, with references to Articles 51, 52 and 55 for models with systemic risk; EU legislative texts are free to reuse. The headings are summarised in original wording and no text of the Regulation or of the General-Purpose AI Code of Practice is reproduced. Check the consolidated text on EUR-Lex and the AI Office for the binding text, delegated acts amending the annexes, templates and guidance. This is a documentation format, not legal advice. Template licence: MIT.

相关模板