An artifact is useful evidence only when it can be connected to the work that created or changed it. Start with the expected artifact and follow its durable identities back through the run.
Inspection order
- Identify the session and run that should have produced the artifact.
- Read the run's terminal event rather than inferring success from UI text.
- Inspect tool events and results for the create or update operation.
- Compare session memory
linkedArtifactswith the actual artifact path or ID. - Inspect traces, checkpoints, and replay evidence tied to the same run.
Common disagreements
| Observation | Useful evidence |
|---|---|
| Artifact is missing | terminal event, tool failure, requested path, capability policy |
| Artifact exists but is stale | observed source revision, edit result, checkpoint diff |
| Memory points to another artifact | memory revision and the update that changed linkedArtifacts |
| UI and stored artifact disagree | persisted artifact identity and the product projection |
| Trace and run history disagree | correlation, session, run, and event IDs on both records |
Do not rewrite historical evidence to make it agree with the current artifact. Preserve the original run and create new work only when a corrected artifact is actually needed.
Continue with Store and replay, Reliability, and Evaluations.