Art.11: Technical Documentation
Maintain technical docs sufficient for conformity assessment.
Last reviewed October 2026
Why Art.11 evidence is hard
Nothing is fired at Article 11. The obligation is to hold documentation an assessor can read before the system ships, and no adversarial test produces a document. Penaxtra contributes one machine-readable slice of it: the AI-BOM export, listing every registered model, endpoint and application with where it was discovered, whether a human verified it, and when it was last seen. Your conformity file carries the rest.
How Penaxtra maps to Art.11
The EU AI Act Art.11 identifier is attached at creation, so a finding reaches the evidence export already in the structure an assessor reads. Twenty-five cross-framework overlap pairs are pre-computed, so where this same weakness also lands on another framework, that control identifier rides the same finding instead of being re-derived. Every finding carries the probe that was sent, a SHA-256 digest of the response it provoked, the tier that decided the verdict and its status history from first observation to close. Identity survives a re-scan: a control you closed and that comes back reopens under the same row with a reopen count, rather than arriving as a new issue.
Art.11 capabilities
Findings tagged with the EU AI Act Art.11 identifier
Penaxtra severity for this control (high)
Cross-framework identifiers attached to the same finding where controls overlap
PDF and JSON evidence export with the control identifier attached
Art.11 control coverage
Findings for Art.11 carry the EU AI Act Art.11 identifier along with the corresponding control identifiers in the other frameworks Penaxtra maps, so one result is reflected across each mapped framework.
Frequently asked
What is Art.11 (Technical Documentation)?
Maintain technical docs sufficient for conformity assessment. It is an EU AI Act control; Penaxtra assesses it at high severity.
How does Penaxtra test for Art.11?
The EU AI Act Art.11 identifier is attached at creation, so a finding reaches the evidence export already in the structure an assessor reads. Twenty-five cross-framework overlap pairs are pre-computed, so where this same weakness also lands on another framework, that control identifier rides the same finding instead of being re-derived. Every finding carries the probe that was sent, a SHA-256 digest of the response it provoked, the tier that decided the verdict and its status history from first observation to close. Identity survives a re-scan: a control you closed and that comes back reopens under the same row with a reopen count, rather than arriving as a new issue.
Does a finding for Art.11 help with an audit?
Each finding is tagged with the EU AI Act Art.11 identifier and exported in the PDF and JSON evidence pack, so it appears on the auditor control list with the identifier already attached.