EU AI Act technical documentation for AI agents (Article 11 & Annex IV)

What Article 11 and Annex IV require

Article 11 requires high-risk AI systems to have technical documentation, and Annex IV lists what it must contain. Much of it is a structured description of the system: what it is, how it was built, and how it behaves.

• A general description of the system and its intended purpose.
• Design choices, key components, and the versions involved.
• How the system was developed, validated, and tested.
• Documentation that exists before market placement and is kept up to date.

How the genome captures it

An Agenomic agent-bundle is a structured, versioned snapshot of an agent. The files in a bundle line up with several Annex IV elements, so the documentation tracks the system instead of drifting from it.

• genome.yaml — the agent definition: prompts, models, tools, permissions, and policies.
• agent.lock.yaml — the pinned, resolved versions and dependencies.
• behavior.contract.yaml — the behavioral expectations the agent is checked against.
• prompts/system.md — the system prompt that shapes behavior.

Producing and versioning the pack

Because the bundle is built and signed per release, your technical documentation is reproducible and diffable rather than a document that goes stale.

• agenomic build produces a reproducible, signed bundle for a release.
• agenomic inspect shows a bundle’s metadata and canonical hash.
• agenomic diff shows what changed between versions, so updates are easy to justify.
• Agenomic Cloud (optional) can gather these into AI Act evidence packs for review.

Scope and limits

Agenomic captures and structures evidence that maps to Annex IV; it does not write your full technical documentation for you, classify your system’s risk tier, or certify compliance. Treat the genome and bundle as the backbone you attach narrative and assessments to.