Results Packets
Understand the durable artifacts that explain Traces, Findings, manifests, generated coverage, and compare output.
What Evidence Is
Evidence is the durable artifact set from a review, compare run, test case workflow, or local artifact inspection. It should be safe to attach to a release ticket or pull request.
Common artifacts
| File | Purpose |
|---|---|
| report.md | Human-readable summary of risks, scenarios, cohorts, and representative traces. |
| results.json | Structured result data for automation and later analysis. |
| traces.jsonl | Trace-level detail for step-by-step inspection. |
| run_manifest.json | Workflow metadata, inputs, outputs, environment, and artifact references. |
| semantic_advisory.json | Optional advisory sidecar when semantic mode is enabled. |
Compare artifacts
Compare runs add files such as regression_report.md, regression_summary.json, regression_traces.json, and nested baseline/candidate audit output.
Agent artifacts
Agent runs can include external call summaries, external call events, local verifier output, generated task/environment pack metadata, variant manifests, and stress manifests when those paths are explicitly configured.