destill.ai · All sectors · Deutsch · Trust Center

For AI Act and GDPR advisers, trainers and auditors, and for companies that deploy AI

The authority asks: show your logs. What can software evidence, and what is still your job?

In a dispute every party has its own logs and photos, and nobody trusts the other side’s data. Proof of Agent Work gives each step of an AI agent a signed, independently time-stamped receipt, and Fortress marks and seals images. The film draws the line between what software evidences and what your organisation must build. Software produces evidence and tools; it does not make anyone compliant.

The filmRequest a pilotBook a call

See also: Trust Center: keys, fingerprints, threat model · Check a receipt yourself

Advisers, trainers and auditors

You are asked what software can evidence for the AI Act and GDPR, and what stays with the organisation. The film and this page draw that line, and you can check a receipt live in a course or an audit.

Companies that deploy AI

When a regulator, an auditor or an insurer asks what your AI did, you want a record that existed at a fixed time and was not changed afterwards.

Insurers and auditors on the other side

Two parties, one case, the same receipts: you check the same receipt with the same open tools and reach the same result, instead of trusting the other side’s logs.

What software can evidence, and what you build yourself

The film sorts it into green (evidence software can produce) and red (your job). Each card says what we cover today and what we do not. Built today: POAW receipts and Fortress marking. Everything marked Roadmap is planned and not available.

Green: time saved

Reconstructing after a request what an AI system did is slow work, and a log that someone with database access could change is weak evidence.

What we cover today: The receipt arises while the agent runs: each step signed, in order, with model and version.

What it does not cover: It does not fill your templates (FRIA, DPIA, records of processing) or track deadlines. Those are on the roadmap.

Green: evidence for logging duties

The AI Act requires logging for high-risk AI (Art. 12), and deployers keep the logs for at least six months (Art. 26(6)). Under the AI Act as amended by the Digital Omnibus, the high-risk duties apply from 2 December 2027 for Annex III and from 2 August 2028 for Annex I; AI literacy (Art. 4) has applied since 2 February 2025.

What we cover today: Signed, time-stamped logs of agent steps (Art. 12, 19 and 26(6)), and a Fortress mark on content you generate, as one building block for Art. 50(2).

What it does not cover: What to log and for how long is the provider’s decision. A mark can be removed with effort. A manifest with C2PA export is on the roadmap.

Sources: AI Act (EU) 2024/1689

Green: collecting proof

In an audit or a dispute you need evidence that others can check without your help.

What we cover today: Hash chain, ML-DSA-65 signature and RFC 3161 time stamp. Change one number and the check fails; anyone can repeat it with OpenSSL.

What it does not cover: A forensic timeline and an evidence package with redaction are on the roadmap. Keys are held in software today; there is no public transparency log and no hosted API yet.

Green: honest arguments on fines

Both the AI Act (Art. 99(7)(g)) and the GDPR (Art. 83(2)(d)) take the technical and organisational measures a party implemented into account when fines are set.

What we cover today: Receipts document that a measure existed and was running.

What it does not cover: They do not predict or lower a fine and do not rule one out. A receipt supports an argument; the authority decides.

Sources: AI Act Art. 99 · GDPR Art. 83

Red: what you build yourself

Training (AI Act Art. 4), responsibilities and oversight (Art. 26), risk management (Art. 9), conformity assessment, EU database registration, the legal basis (GDPR Art. 6), the AI notice (Art. 50(1)), decisions on reporting (Art. 73), contracts (processor agreements, DORA Art. 28) and governance.

What we cover today: A receipt can show that a person decided. It does not train anyone, assign responsibility or take the decision.

What it does not cover: All of the list on the left. It stays with your organisation.

The film

The opening scene, as a short clip.

The full explainer

Chapters

What you get

Each item carries its status from our feature register: Built, Pilot or Roadmap. Hover a label for the evidence behind it.

The legal frame

Where a receipt helps you evidence an obligation. It does not fulfil the obligation for you and does not make anyone conform with the law by itself. Not legal advice.

AI Act Art. 12, 19 and 26(6)

Logging for high-risk AI, and keeping the logs. Whether your use case is high-risk is an assessment for your legal team. Where it is, a receipt helps you evidence that a log existed unchanged at a fixed time.

Source: eur-lex.europa.eu

AI Act Art. 50

Marking of AI-generated or manipulated content and the notice duty. Fortress marks can help you evidence that content was marked; whether and how Art. 50 applies to you is a legal assessment.

Source: eur-lex.europa.eu

GDPR Art. 83(2)(d)

Technical and organisational measures are one factor when a fine is set. A receipt can show that a measure was running; it does not set or lower the fine.

Source: gdpr-info.eu

Product Liability Directive (EU) 2024/2853, Art. 9 and 10

A court can order disclosure of evidence (Art. 9), and a defect can be presumed where it is not disclosed (Art. 10). Evidence that existed at a fixed time helps you produce your side; what a court does with it is not ours to say.

Source: eur-lex.europa.eu

The pilot: 8 weeks, two parties, price after scoping

Scope

One shared process between two parties, for example a company and its insurer or auditor. Both check the same receipts with the same open tools. Final report with go/no-go. Duration: 8 weeks.

Price frame: Price after scoping.

Success criteria, agreed in writing at kick-off

  • At least 99 % of AI steps in the pilot workflow produce a verifiable receipt.
  • Both parties verify the same receipt independently and reach the same result.
  • Extra effort per work step is measured; we set the target together at kick-off.

Source: our written pilot offer; the targets are what we commit to measure, not results from an earlier pilot.

What you provide

  • One concrete workflow and an owner
  • Test data or test images and access to a test environment
  • Contacts from IT and compliance or audit
  • Internet access when signing (for the time stamp)
  • Your own legal assessment
  • Consent and contacts from both parties

Want the written pilot offer? Choose "Talk about a pilot" below and we send it with our reply.