# What belongs in a coding-agent verification evidence bundle?

> Canonical page: https://codevetter.com/verification-evidence-bundle

A verification evidence bundle is the portable record behind a verdict. It should let a person, CI system, or later evaluation understand exactly what was checked without relying on a screenshot or a model summary.

## Required identities

The bundle should bind the task, repository, base revision, agent change, verifier version, environment, and attempt. Without those identities, a passing output can be accidentally attached to the wrong patch or repeated under different conditions.

## Execution records

For each check, retain the normalized command or runner identity, start and finish state, exit result, timeout or cancellation state, and bounded output. Record artifacts such as screenshots or reports by path and digest when they contribute to the verdict. Do not hide environment failures inside a generic test failure.

## Verdict and uncertainty

A useful verdict separates passed requirements, reproduced failures, regressions, pre-existing failures, infrastructure failures, and requirements that remain unverified. The bundle should fail closed when an authoritative check is missing instead of filling the gap with a confidence score.

## Redaction and portability

Evidence should be useful without leaking secrets or entire private repositories. Retain only the necessary excerpts and metadata, enforce output bounds, redact sensitive values, and make truncation explicit. JSON is useful for automation; Markdown and self-contained HTML are useful for human inspection.

## Re-check linkage

When a failure is fixed, the new bundle should reference the earlier attempt and preserve the failing evidence. That creates a closure trail: failed behavior, corrective change, passing check, and regression result.

CodeVetter's product direction makes the machine-readable verification bundle a primary surface. Completed reviews can already export fail-closed JSON, Markdown, and self-contained offline HTML evidence, while the broader agent-task evaluation contracts remain explicit about qualification and missing proof.

**CTA:** Inspect the benchmark data format or download CodeVetter to review evidence locally.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)