For teams Agents Integrations Governed Runtime Pricing Enterprise Security Academy Compare Blog
Book a demo Sign in
AI Provenance

An action without provenance is an action without an author.

Provenance is the oldest trust technology we have. It is how a painting proves it is not a forgery and how a dataset proves where it came from. AI agents now take actions inside your business. Those actions need the same thing.

What AI provenance means

AI provenance is the verifiable record of an AI action's origin and journey: who requested it, which agent and model produced it, what data it touched, who approved it, and what it changed.

The word comes from the art world, where provenance is the documented chain of custody that makes an object trustworthy. Data teams borrowed it for lineage. Now agents force the question onto behaviour itself: not where did this file come from, but what did our AI do, and on whose authority.

Content provenance is solved talk. Action provenance is the open problem.

Most of the 2026 provenance conversation is about media: C2PA credentials, watermarking, proving whether AI made an image. That work matters, and it answers a different question.

Content provenance

Where did this artefact come from? Was it AI-generated? Authenticates files: images, video, documents. The C2PA and watermarking conversation.

Action provenance

What did the AI do? It queried the CRM, drafted the email, updated the record. On whose request, with which model, under whose approval. Accounts for behaviour, not files. This is where Renly works.

A chatbot produces text a human then acts on, so the human is the author of record. An agent acts directly. Once AI takes the action itself, provenance stops being optional metadata and becomes the difference between a system you can defend and one you cannot.

The provenance thread

Renly treats every agent action as one continuous thread. Each stage is recorded and correlated to the same action, so the whole journey can be read back later as a single account.

The provenance thread of one AI action One continuous thread connects five recorded stages of an AI action: the request by a user, the agent and model that propose, the human approval, the execution against the target system, and the correlated provenance record. Request user Proposal agent + model Approval human Action target system Provenance record
One thread, end to end. Break any link and it is no longer provenance, it is just logging.

What the record contains

Each recorded action in Renly carries the fields an auditor actually asks for, correlated into one chain with timestamps.

Requester
The person or workflow that asked for the action.
Agent
Which agent handled it, by name and configuration.
Model
Which model produced the proposal, whichever provider it runs on.
Inputs
What the agent was given and what it read.
Approval
Who approved the write, where a gate applied, and what they saw.
Outcome
What the target system returned. Not what the agent intended, what actually happened.

This is why provenance is not logging. Logs are fragments: one system's view, in its own format, in its own place. Provenance is the same action traced end to end. You can grep logs. You answer to an auditor with provenance.

Common questions

What is AI provenance?

AI provenance is the verifiable record of an AI action's origin and journey: who requested it, which agent and model produced it, what data it touched, who approved it, and what it changed. The term borrows from art and data lineage, where provenance is the documented chain of custody that makes an object trustworthy.

How is action provenance different from content provenance?

Content provenance, the C2PA and watermarking conversation, tells you where a piece of media came from and whether AI made it. Action provenance tells you what an AI agent actually did inside your business: the request, the model, the approval, and the outcome. Content provenance authenticates artefacts. Action provenance accounts for behaviour.

Why does provenance matter for AI agents specifically?

A chatbot produces text a human then acts on. An agent acts directly: it writes to your CRM, sends the email, updates the record. Once AI takes the action itself, the question shifts from "is this output good" to "can we account for what happened". Agents without provenance are actions without an author.

What does a provenance record contain in Renly?

The requesting user, the agent, the model that produced the proposal, the inputs, the approval decision where a gate applied, the outputs, and the response from the target system, correlated into one chain with timestamps.

Is provenance the same as logging?

No. Logs are fragments: one system's view, in one place, in its own format. Provenance is a chain: the same action traced end to end, from request to outcome, with each step correlated to the others.

Renly is the governed runtime for AI agents. The agents run the work. Every action carries its provenance.

See how the runtime works Read: AI accountability