# Evidence and signatures

> Bind completion claims to exact source, tests, policy, and reviewer decisions.

Source: https://accd.github.io/verchestra/docs/concepts/evidence-and-signatures/
Content digest: `sha256:1842627d24a40206f745ca63e07af82b160a11418d608a45db00b2349b83c60c`

Evidence is structured, source-bound proof. Typical evidence includes commands, exit status, selected output, artifact digests, environment facts, and redaction metadata.

Signatures bind reports and decisions to:

- the Execution Package;
- the source commit;
- the evidence manifest;
- the verifier identity;
- the applicable policy version.

A signature proves integrity and provenance, not correctness by itself. Correctness still depends on meaningful tests, independent verification, and accountable review.