Artifact
Final deliverableMessages explain formation. The artifact is the result you actually use.
Workflow
Artifacts
Artifacts hold the final output of execution. They exist so the deliverable has a durable destination with formation context instead of being buried in a run transcript.
Guide summary
Use this page to understand the surface before you act inside it.
Use Artifacts as the finished deliverable layer, not as a dump of execution messages.
Guide type
WorkflowThis guide reflects the current product workflow and surface ownership.
Sections
7Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Main risk
No artifact generatedThis usually means the run did not reach a successful final packaging posture.
Related action
Inspect linked runThe run explains how the artifact formed and what blocked it if it never appeared.
Guide section
What it is
An artifact is the final packaged deliverable produced by a run.
When to use it
Use the artifact whenever you need the deliverable rather than the run mechanics.
Where to find it
Find artifacts in the Artifacts index and on linked run detail pages.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Treating run messages as the final result
Related action
Use the “No Artifact generated” guide if the expected deliverable never landed.
Guide section
Why it matters
It separates finished output from execution conversation and makes the result easier to copy, review, improve, and reuse.
Guide section
How it fits into the workflow
Artifacts are the final output of the run lifecycle.
Guide section
Step-by-step usage
- Open the artifact from the run or artifacts index.
- Review the summary and final content.
- Check assumptions, risks, and next steps if present.
- Use improve or follow-up actions when available.
- Return to Replay if you need proof or diagnostic detail.
Guide section
Inputs and outputs
Inputs needed
A completed or packaging-ready run
Outputs produced
A finished deliverable
Formation summary
Linked execution context
Optional improvement path
Guide section
Common mistakes
- Treating run messages as the final result
- Skipping assumptions and risk notes on important output
- Ignoring the linked run when an artifact feels weaker than expected
Guide section
Troubleshooting
If no artifact appears, verify whether the run completed, whether final packaging failed, and whether review blocked the output.