Operation Artifact
The operation artifact represents the record of multi-step bot or runtime work. Use operation artifacts to review requests, turns, tool calls, outputs, and final status.
When To Use This Kind
- Choose this kind when the artifact's meaning matches the operational object, not merely because of a file extension.
- Attach source or rendered files as blobs when the artifact has file-backed content.
- Link this artifact to sources, outputs, operations, and related context so reviewers can follow the evidence chain.
Data Contract
Kind data contract: OperationData with fields family, source, status, owner, target_artifact_id, parent_operation_id, root_operation_id.
Common artifact fields still apply: title, summary, status, visibility, metadata, blobs, links, and events.
Review Checklist
- Confirm the artifact kind matches what the team needs to review.
- Check available blobs before assuming source or rendered content exists.
- Follow links to understand provenance and downstream outputs.
- Review events for creation, updates, renders, tool work, and failures.
Media To Add
- Screenshot: operation artifact detail page with kind data, blobs, links, and events labeled. It helps readers understand how this artifact appears in the app. Source: sample workspace artifact of this kind.