WARRANTWhat audit-ready evidence actually is.
An autonomous agent in a high-risk deployment takes many consequential actions in a single run. When an auditor opens an inquiry in 2027 about an action from 2026, the question is never "show me uptime that day". The question is narrower: show me what the agent did at this moment, under what authorisation, against which obligation, and prove the record has not been edited since. Evidence is audit-ready when it can answer that question without the deployer scrambling to reconstruct behaviour after the fact.
That resolves into four requirements the evidence must satisfy. It is a per-action record. Each record names the governing obligation. Each record captures the authorisation. The record retains automatically over the system lifetime and is independently verifiable. The rest of this note works each requirement against the EU AI Act text, so a deployer can read the spec against any candidate stack. The architecture behind these properties is set out in the four-layer evidence stack; this note is the requirements view a deployer holds a vendor to.
Article 12(1) is the dated, penalty-backed obligation underneath all of this. The application date is 2 August 2026, subject to a provisional deferral to 2 December 2027 for Annex III standalone systems under the May 2026 Digital Omnibus. Non-compliance is reachable under Article 99(4) at up to EUR 15 million or 3 percent of global annual turnover. What the sentence does not do is fix the shape of the record. The four requirements below are what turn a bare logging obligation into evidence an auditor accepts.
It is a record per action.
The first requirement is granularity. Article 12(1) requires recording of events over the lifetime of the system, but it does not say whether a record means one running log per system or a discrete record for each autonomous action. For a single-pass model the distinction is academic. For an agent that takes a chain of consequential actions in one run, it is the whole question. An auditor cannot grade an action the deployer can only show buried inside a system-wide log.
So audit-ready evidence makes each action an addressable record. The per-action unit carries, at minimum, the actor, the action, the subject, the inputs, the outputs, and the timestamp, expressed in the schema as trace.actions[*]. That is the smallest unit a regulator's question maps onto. Whether the draft classification Guidelines treat the agent or the step as the unit of assessment is still an open boundary, examined in the per-action records question; either way, evidence built per action survives both readings.
Each record names the governing obligation.
The second requirement is that the record cites the specific obligation it answers to, down to the sub-clause, not the regulation in the abstract. "EU AI Act compliant" is not evidence. "Article 12(2)(c), monitoring under Article 26(5)" is. An audit-ready record names the article, the paragraph, and the sub-paragraph, so an auditor traces the record to the canonical text rather than to the vendor's interpretation of it.
The mapping is concrete. The per-action record under trace.actions[*] answers Article 12(1). The risk-situation events under Article 12(2)(a) map to the per-action risk assessment. The post-market monitoring events under Article 12(2)(b) map to the per-action outcome roll-up. The human-oversight monitoring events under Article 12(2)(c) map to the per-action oversight fields and resolve against Article 26(5). The line-by-line field-to-clause map is set out in Article 12, line by line.
Each record captures the authorisation.
The third requirement is that the record does not just say what the agent did; it says whether the agent was allowed to do it. For each action the record carries the authorisation: whether the action sat within the system's intended purpose, expressed as within_purpose, and whether the required human oversight was present, carried in the authorization_envelope.* fields. An action that fell outside the intended purpose, or that should have had a human in the loop and did not, is exactly what an auditor is looking for.
This is where the record-keeping obligation meets the deployer's standing duties. A deployer that runs a high-risk agentic system carries the Article 26 obligations and signs its name to what leaves the building, including the human oversight measures under Article 26(2) and the monitoring under Article 26(5). The authorisation fields are what let a record demonstrate those duties were met for each action rather than asserted at the system level. The full deployer duty set is in the Article 26 deployer obligations, line by line.
It retains over the system lifetime.
The fourth requirement is retention, and it is the one a general-purpose telemetry stack quietly fails. Article 12(1) scopes recording to the lifetime of the system. Article 19(1) puts a floor under it: logs must be kept for at least six months, appropriate to the intended purpose, unless other Union or national law requires longer. Sectoral law frequently requires far longer. MiFID II runs five to seven years. The Medical Device Regulation runs ten to fifteen years for implantable devices.
The practical test is whether retention is a property of the evidence system or a retention plan bolted onto a telemetry tool. Audit-ready evidence retains automatically over the system lifetime; it does not depend on someone remembering to extend a retention window before logs rotate. A record that was rotated out cannot be reconstructed after the fact, and a record reconstructed after the fact cannot be made audit-ready retroactively.
It is independently verifiable.
The fifth requirement is the one that separates a record from a claim. Audit-ready evidence is independently verifiable: an auditor can confirm the record is unchanged since the action on their own machine, without contacting the vendor and without trusting the vendor's storage. The property lives in the record itself and resolves against an external public reference the vendor does not operate. None of it depends on the vendor being honest, present, or even still in business.
The failure mode this requirement closes is the deposition question. A record held only in the vendor's database, presented as the vendor presents it today, has a known weakness: staff turnover, data migration, a deliberate edit by an insider. A regulator who asks "who attests this is unchanged?" gets one answer, the vendor, and that answer collapses on chain of custody. An independently verifiable record inverts the trust assumption: the auditor checks the record, not the vendor. An audit-ready record is one a court can trust without trusting the company that produced it.
The record shape, read against the text.
Put the five requirements together and the shape of an audit-ready record is exact. It is a per-action unit. Each unit carries the field that names its obligation, the fields that capture its authorisation, and the events Article 12(2) calls relevant. The whole set retains over the system lifetime to the Article 19(1) floor. And the set is independently verifiable. A deployer can score any candidate evidence stack against this shape line by line.
Questions a deployer asks first.
Read the source directly.
- Regulation (EU) 2024/1689 · EUR-Lex CELEX:32024R1689
- Article 12 record-keeping · annotated text
- Article 19 automatically generated logs · retention floor
- Article 26 obligations of deployers of high-risk AI systems
- Article 99 penalties
- The four-layer evidence stack · the architecture behind these properties
- Article 12, line by line · the field-to-clause map in full
- Article 26 deployer obligations · who signs for the agent
- Regulator-grade evals · how the citations are held to canonical text
Authored by Warrant Compliance, the regulatory-analysis function at Warrant. [email protected]. Editorial commentary on regulatory text and the shape of audit-ready evidence. Not legal advice. The verbatim quotation of Article 12(1) reflects the official English-language text of Regulation (EU) 2024/1689 as published in the Official Journal of the European Union on 12 July 2024. Retention references are to Article 19(1); deployer references are to Article 26.