---
title: "Provenance (agent provenance)"
description: "Agent provenance is the record of which agent, on which platform and under which identity, created or changed an artifact, and when, so work stays attributable across agents and sessions."
canonical: "https://agentdrive.sh/glossary/provenance"
---
# Provenance (agent provenance)

> For the complete documentation index, see [llms.txt](https://agentdrive.sh/llms.txt). Every docs page is also served as markdown at its URL plus `.md`, and the full docs are in one file at [llms-full.txt](https://agentdrive.sh/llms-full.txt).

> Agent provenance is the record of which agent, on which platform and under which identity, created or changed an artifact, and when, so work stays attributable across agents and sessions.

Source: https://agentdrive.sh/glossary/provenance. Part of the AgentDrive glossary: https://agentdrive.sh/glossary.

When several coding agents work in one project, provenance answers which agent wrote a file, which session touched it and what it was doing at the time. It is built from records written when each change happens, such as version history, activity events and run logs, rather than reconstructed afterwards from memory or commit messages.

## In AgentDrive

AgentDrive keeps provenance in file versions that record the actor, activity events and run records stamped with the agent platform, and runs can carry a role. Each synced session becomes a run. Every plan includes the provenance timeline.

## Related terms

- [Principal (AgentDrive)](https://agentdrive.sh/glossary/principal/index.md): In AgentDrive, a principal is the identity behind an API key: a human or a team that owns workspaces, holds the plan and is billed, whichever agents act on its behalf.
- [Session sync](https://agentdrive.sh/glossary/session-sync/index.md): Session sync copies a coding-agent session from the machine it runs on into a shared workspace as it happens, so another agent or another machine can read and resume it.
- [Content-addressed storage](https://agentdrive.sh/glossary/content-addressed-storage/index.md): Content-addressed storage keeps each piece of data under a key derived from its content, usually a cryptographic hash, so identical content is stored once and a stored object never changes.

## Go deeper

- [Cross-agent identity](https://agentdrive.sh/docs/concepts/cross-agent-identity)
- [MCP tools: provenance](https://agentdrive.sh/docs/mcp-tools#provenance)
- [Manifesto](https://agentdrive.sh/manifesto)

