EU AI Act for
Autonomous Agents
“The EU AI Act does not ask you to trust your agent. It asks you to prove what it did — and why it was allowed to do it.”
The Compliance Gap for Agentic AI
The EU AI Act (Regulation 2024/1689) places strict obligations on high-risk AI systems. But autonomous agents present a unique challenge: they make consequential decisions and take real actions without continuous human supervision. Traditional logging and documentation practices were designed for passive prediction systems, not for agents that modify files, send emails, or trigger financial transactions.
This article maps the EU AI Act's three most technically demanding articles — 13, 14, and 17 — to a concrete evidence architecture that autonomous AI teams can implement today. We show how VEX Protocol's Evidence Capsules provide the technical substrate for compliance without duplicate instrumentation.
Article 13: Transparency and Provision of Information
The requirement:High-risk AI systems must produce outputs that are interpretable by users and deployers. Users must be informed they are interacting with an AI system, and the system must provide “clear and meaningful information” about its capabilities and limitations.
The agentic challenge:An autonomous agent may take dozens of tool calls to complete a task. A single “success” response tells you nothing about what files were read, what APIs were called, or what parameters were passed. Transparency requires per-action attribution, not just task-level summaries.
The evidence architecture: Each governed action produces an Evidence Capsule containing:
Article 14: Human Oversight
The requirement:High-risk AI systems must be designed to allow human operators to “intervene, override, or stop operation at any time.” Oversight must be technically enforceable — not just documented in a policy manual.
The agentic challenge: An agent with unconditional tool authority cannot be overridden in practice. By the time a human reviews the action, the file has been deleted, the email sent, or the database modified. Post-hoc review is not oversight; it is incident response.
The evidence architecture: VEX Protocol implements execution boundary governance:
This is not logging. This is governance at the execution boundary — the only place where human oversight can be technically enforced for autonomous systems.
Article 17: Quality Management System
The requirement: Providers must implement a quality management system covering risk management, data governance, technical documentation, and post-market monitoring. Records must be complete, accurate, and available for regulatory inspection.
The agentic challenge: Traditional audit trails can be modified, deleted, or truncated. A quality management system built on mutable logs cannot satisfy the integrity requirements of Article 17 — especially when the agent itself has write access to the log storage.
The evidence architecture: Cryptographic commitment ensures tamper-evidence:
Merkle-chain integrity
Each Evidence Capsule is hashed and linked into a Merkle tree. Modifying any historical capsule invalidates the chain, making tampering cryptographically detectable.
Merkle Audit Trail — ProvnAI Glossary
Separation of duties
The evidence system operates independently from the agent runtime. The agent cannot modify its own audit trail because the trail is produced by a separate, isolated governance component.
TEE Isolation — ProvnAI Glossary
Temporal attestation
Each capsule includes a timestamp from a trusted time source, preventing backdating or reordering of events after the fact.
Witness Log — ProvnAI Glossary
One Architecture, Multiple Frameworks
The same evidence architecture that satisfies EU AI Act Articles 13, 14, and 17 also supports:
ICT risk management and incident reporting — Evidence Capsules provide structured, attributable incident records.
System availability and processing integrity — tamper-evident logs support auditor review of control effectiveness.
Cybersecurity risk management — execution boundary governance maps to 'appropriate technical measures' for critical entities.
AI risk assessment and treatment — Evidence Capsules provide objective evidence of AI system behavior and controls.
Implementation: From Theory to Production
Teams do not need to rebuild their agent infrastructure to implement evidence-based governance. VEX Protocol integrates at the execution boundary — the narrowest possible integration point:
Design for compliance from the execution layer.
See how VEX Protocol maps to EU AI Act, DORA, and SOC 2 requirements with a single evidence architecture.
What is an MCP Security Proxy? Real Attacks, Real Policies
How an MCP security proxy intercepts tool calls before execution, blocking prompt injection, SSRF, and path traversal.
MCP Security in Production: The Definitive 2026 Guide
A layer-by-layer guide to securing MCP deployments — attack surface, five-layer defense, and production checklist.
EU AI Act for Agentic AI: Technical Compliance Requirements
High-risk classification, Articles 13/14/17, and the evidence architecture that supports compliance.
OWASP Top 10 for AI Agents: The 2026 Threat Model
The definitive vulnerability taxonomy for autonomous AI deployments — 10 risk categories with mitigations.