Document template · eu.ai_act.ai_system_documentation
AI System Technical Documentation (Annex IV)
- Render-verified
- Official document
- Version 1.0.0
Technical documentation for a high-risk AI system, drawn up and kept up-to-date by the provider before placing the system on the market or putting it into service under Art. 11 and Annex IV of Regulation (EU) 2024/1689 (AI Act). This PDF is the human-readable summary of the underlying technical file; source artefacts (model cards, training logs, test datasets) are referenced, not inlined.
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 53 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| reference | Optional | string | |
| document_date | Optional | date | |
| provider | Required | object | Provider of the high-risk AI system (Art. 3(3), Art. 16 AI Act). |
| provider.name | Required | string | |
| provider.address | Required | string | |
| provider.contact_email | Required | string | |
| provider.authorised_representative | Optional | object | Authorised representative established in the Union (Art. 22 AI Act), where the provider is established in a third country. |
| system | Required | object | General description of the AI system (Annex IV §1). |
| system.name | Required | string | |
| system.version | Required | string | |
| system.intended_purpose | Required | string | |
| system.high_risk_category | Required | enum | Annex III high-risk category under which the system is classified. |
| system.description_of_hardware_software | Required | string | |
| system.integration_context | Required | string | |
| ce_marking | Required | object | CE marking and conformity assessment route (Art. 43, Art. 48 AI Act). |
| ce_marking.applicable | Required | boolean | |
| ce_marking.conformity_assessment_route | Required | enum | |
| ce_marking.notified_body | Optional | string | |
| ce_marking.notified_body_number | Optional | string | |
| design | Required | object | Design specifications of the system (Annex IV §2). |
| design.optimisation_objectives | Required | array of string | |
| design.key_design_choices | Required | array of string | |
| design.relevance_of_input_data | Required | string | |
| data_governance | Required | object | Data and data governance measures (Art. 10 AI Act, Annex IV §2(d)). |
| data_governance.training_data_summary | Required | string | |
| data_governance.validation_data_summary | Required | string | |
| data_governance.test_data_summary | Required | string | |
| data_governance.data_categories | Required | array of string | |
| data_governance.bias_mitigation_measures | Required | array of string | |
| data_governance.data_provenance | Required | array of string |
+23 more fields — the full JSON Schema is available in the dashboard and via the API.
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "eu.ai_act.ai_system_documentation",
"data": { ... },
"options": {"language": "en"}
}' -o ai-system-documentation.pdf Frequently asked questions
What is “AI System Technical Documentation (Annex IV)”?
Technical documentation for a high-risk AI system, drawn up and kept up-to-date by the provider before placing the system on the market or putting it into service under Art. 11 and Annex IV of Regulation (EU) 2024/1689 (AI Act). This PDF is the human-readable summary of the underlying technical file; source artefacts (model cards, training logs, test datasets) are referenced, not inlined. On papii this document is available as template eu.ai_act.ai_system_documentation: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a AI System Technical Documentation (Annex IV) with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the AI System Technical Documentation (Annex IV) template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.