What Evidence is

Your CAMP assessment records what you say about your program. Evidence asks a harder question: how much of that can you actually prove? It is the proof-and-health layer of Pytheus, and it sits on top of the Brain, the knowledge graph that links your score all the way down to the artifacts behind it.

A separate axis from readiness

A self-reported CAMP answer is a claim. Evidence is the proof. Those are two different things, and Evidence keeps them apart. A control can be marked as covered in a framework readiness view and still have no independent evidence behind it. Evidence exists precisely to surface that distinction, so you know what is genuinely demonstrated versus merely asserted.

What the page shows

Evidence maps your framework controls to the CAMP capabilities that support them, then classifies each control by the strongest proof it holds. Two headline numbers fall out:

• Program coverage: the share of controls backed by fresh, independent evidence.

• Backed coverage: the share with any supporting proof, verified or attested.

A library of documents and evidence requests sits alongside, so you can see what has been provided and what is still outstanding.

Shared with the Brain

Evidence and the Brain graph are two views of the same page. Evidence is the summary; the Brain is the graph you can explore. They always tell the same story, because the graph carries the same verification states Evidence derives.

Evidence never changes your Pytheus Score. It tells you how much of that score you could defend in an audit, which is a different and equally important question.

The classification is explained in Verification states. The graph beneath it is described in The Pytheus Brain.