Evidence note · reviewed 29 July 2026


A link beside an answer is not yet evidence.

A reviewer must be able to find the exact source, see what supports the claim, understand authority and time, and reconstruct how the system arrived there.

Minimum answer packet

Source identity

Stable document, version, date, owner and location inside the governed corpus.

Support span

The passage or structured record that actually supports the claim, not just a nearby page.

Authority

Who issued the source, for which scope, and whether a later or controlling source exists.

Retrieval trace

Query, filters, access role, retrieved candidates and model/runtime version.

Uncertainty

Conflicts, missing support, qualifications and a refusal when evidence is insufficient.

Review receipt

The human decision, accepted use and retained evidence for relied-on work.

Acceptance tests matter more than eloquence

Test known answers, unanswerable questions, conflicting sources, revoked authority, access boundaries and adversarial instructions. A fluent unsupported answer is a failure.

Evidence boundary: citations reduce review cost; they do not make the model a legal, financial or medical decision-maker.

Inspect Answer Assurance →

Ask for the packet, not the confidence score.

Open the Evidence Room