Skip to main content
Agent Artifact is a durable, portable work product with its own identity, versions, sources, permissions, execution, access control and history.
The useful result of an Agent Application is often the work it produces, not the conversation around it. A message belongs to a conversation timeline. An artifact has its own address and lifecycle. A user can revise it, compare versions, share it outside the original conversation, or use it as input to later work. Discussing a spreadsheet is different from having the spreadsheet.

​
Content and record

The content layer holds the bytes that render or run in a compatible environment, including structured data, view state, and executable actions. The record layer holds provenance, permissions, comments, versions, and links to the agent or process that maintains the artifact. When an artifact moves between environments, its record can travel as a verifiable sidecar. Remove that record and the content should still be a usable document or application. The proposed standards sequence begins with artifacts. See Companion documents and the paper, section 13.