> For the complete documentation index, see [llms.txt](https://powv-protocol.gitbook.io/powv-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://powv-protocol.gitbook.io/powv-protocol-docs/verifiable-evidence.md).

# Verifiable Evidence

The public dimensions used to reason about trustworthy physical evidence.

PoWV treats evidence as a structured basis for evaluating a physical claim, rather than as an isolated file, sensor reading, or database row.

![PoWV evidence assurance model](https://1151534167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWO75canbSRCuzukBrP8n%2Fuploads%2F47zLa2w2gnFR6yzuuo7G%2Fassurance-model.svg?alt=media)

## Six assurance dimensions

| Dimension     | Evaluation question                                                                     |
| ------------- | --------------------------------------------------------------------------------------- |
| Provenance    | Can the claim be associated with an authorized physical and operational context?        |
| Integrity     | Can unauthorized modification be detected during review?                                |
| Uniqueness    | Can repeated, conflicting, or reused claims be identified?                              |
| Continuity    | Does the evidence remain coherent across custody and system boundaries?                 |
| Reviewability | Can an authorized reviewer trace the basis of a decision?                               |
| Resilience    | Can evidence remain usable when operations face constrained or intermittent conditions? |

A claim may be strong in one dimension and weak in another. PoWV's public model therefore avoids treating “verified” as a single unexplained label.

## Evidence outcomes

At a public conceptual level, evidence evaluation may lead to:

* **supported:** the available evidence satisfies the applicable assurance policy;
* **exception:** the evidence requires authorized review or additional support;
* **unsupported:** the claim does not satisfy the applicable assurance requirements.

These are assurance outcomes, not descriptions of internal decision rules.

## Explore the evidence model

* [Evidence Model](/powv-protocol-docs/verifiable-evidence/evidence-model.md)
* [Assurance Metrics](/powv-protocol-docs/verifiable-evidence/assurance-metrics.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://powv-protocol.gitbook.io/powv-protocol-docs/verifiable-evidence.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.