Back to observatory
Application10 min read

EU AI Act and automated decisions: how to document an agent's reasoning

On May 7, 2026, the European Parliament approved the Digital Omnibus agreement modifying the EU AI Act timelines. Annex III deadlines were deferred to December 2, 2027, Annex I to August 2, 2028. But Article 50 — governing transparency obligations for AI systems — remains confirmed for August 2, 2026.

This means something very concrete for anyone developing or using AI agents in Europe: in a few months, you'll need to be able to document how your agent reaches its decisions. Not generically. In a structured, verifiable way that an auditor can understand.

The "explainability" problem with agents

The AI Act uses the term "transparency," but what it really asks for is the ability to reconstruct the reasoning behind an automated decision. For a rule-based system, this is trivial: the rule is the reasoning.

For an AI agent based on a language model, it's an open problem. The model doesn't "reason" in the traditional sense. It produces statistically probable outputs based on learned patterns. There's no "decision pathway" that can be extracted and presented to an auditor.

This creates an enormous gap between what the law requires and what the technology can natively offer.

DAMM as a native documentation layer

The DAMM framework solves this gap not by trying to make the model explainable — which is still an unsolved problem in AI research — but by creating a structured documentation layer that wraps every agent decision.

When an agent analyzes a decision through DAMM, the framework automatically produces a report documenting:

Delimitation: what were the operational boundaries? Did the agent operate within or outside its scope? What constraints were active?

Asymmetry: what was the ratio between potential gain and potential loss? How was it calculated? What factors were considered?

Margin: was there sufficient room for maneuver to correct the action? In which dimensions (financial, temporal, relational)?

Minimum Move: was the executed action the smallest and most reversible version possible? If not, why was a broader action chosen?

This report doesn't explain *how* the model generated the output. It explains *through what structured process* the output was evaluated before being executed. And that's exactly what the AI Act requires.

Article 50 in practice: what's actually needed

Article 50 of the AI Act establishes three fundamental requirements for systems that generate automated decisions:

1. Notification: the user must know they're interacting with an AI system and that decisions are automated.

2. Explanation: for decisions with significant impact, it must be possible to provide an understandable explanation of the decision-making process.

3. Traceability: a verifiable log must exist of decisions made, data considered, and criteria applied.

DAMM satisfies all three requirements natively:

  • The DAMM report always includes system identification as "decision assisted by DAMM framework" — built-in notification
  • The 4 pillars provide an explanation structure that an auditor can follow without advanced technical expertise
  • The Health Score, individual pillar scores, and final verdict create a structured, queryable log

Implementation for compliance

For a team that needs to make their AI agents compliant with Article 50, DAMM integration follows a simple pattern:

Pre-decision: the agent sends the decision context to DAMM before acting. The context includes: the decision to make, available options, known constraints, and urgency level.

Analysis: DAMM evaluates the decision through the 4 pillars and calculates the Health Score. Each step is recorded.

Post-decision: the DAMM report is archived alongside the executed decision, creating an immutable record linking the action to the evaluation process.

Audit: during verification, the auditor can reconstruct the entire decision chain: context → DAMM analysis → Health Score → executed action → result.

The competitive advantage of early compliance

Companies that integrate DAMM into their AI agents before the Article 50 deadline aren't just avoiding sanctions. They're building a competitive advantage.

An AI agent that produces a structured audit trail for every decision is an agent that can be proposed to enterprise clients, used in regulated sectors, and presented to investors with a documented risk profile.

In a market where most AI agents operate as black boxes, decision transparency becomes a differentiator. Not because transparency is an abstract value, but because it solves a concrete problem: trust.

Beyond compliance: better decisions

The most underappreciated aspect of decision documentation is that it improves the decisions themselves. An agent that must articulate its evaluation through 4 structured pillars makes better decisions than an agent that operates without structure — not because it's smarter, but because it's forced to consider dimensions it would otherwise ignore.

Delimitation prevents scope creep. Asymmetry reveals hidden risks. Margin prevents irreversible decisions without a safety net. Minimum Move favors the incremental approach.

The EU AI Act is asking for something companies should be doing anyway: giving structure to the decisions of their autonomous agents. DAMM is the framework that makes it possible.

Want to go deeper? Read the complete book