allv Artifacts
Artifacts are durable outputs linked to the run and workflow that created them. Assign ownership, move through review and approval, publish when ready, and keep the execution evidence attached throughout the lifecycle.
Artifacts are not vague outputs. They are first-class records with lifecycle, assignment, approval, and publishing state.
Artifact Review
Run-linked outputLinked to workflow Weekly Ops Brief, run #8f21d4, assigned to the release owner, and waiting for approval before publish.
Assigned to ops@team.com for final review.
Ready for review with approval and publishing controls still intact.
The underlying run and workflow remain one click away when context matters.
Why Artifacts Matter
Artifacts keep the output after the run finishes so operators can review, assign, approve, and publish it later.
Each artifact moves through explicit states such as draft, ready for review, approved, published, or archived.
Artifacts stay attached to the workflow, run, and step that produced them so review never loses context.
Lifecycle
Initial output captured from a run and ready for operator review.
Prepared for handoff or approval without leaving the workspace.
Reviewed and cleared for use by the right operator or owner.
Final output shipped or promoted with publishing metadata preserved.
Kept for history after the active review cycle is complete.
Review Controls
Route an artifact to the teammate who should own the review or publish decision.
Keep approved-at and approved-by state attached to the same artifact record.
Track what was published, by whom, and when the output left draft review.
Open the underlying run when someone needs the execution trace that produced the artifact.
Related features
Summarize created and published deliverables alongside the runs and approvals behind them.
See how multi-step workflows create durable outputs that move through review, approval, and publishing.
Start from shipped workflow templates when you want repeatable output and a clear review path.
Use artifacts when a run result needs ownership, lifecycle, and evidence after execution.
Artifacts stay tied to the workflow, run, and approval history that produced them.