> 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/architecture/trust-domains.md).

# Trust Domains

The public separation between physical context, evidence assurance, and authorized use.

The public PoWV architecture separates responsibility into three trust domains. This prevents an important category error: confusing a physical observation, an assurance decision, and a downstream business action.

## Domain responsibilities

| Domain             | Owns                                                                               | Does not establish alone                                |
| ------------------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------- |
| Physical Context   | The asset, event, measurement, custody, time, and location being claimed           | Whether the claim is sufficiently trustworthy           |
| Evidence Assurance | The evaluation of provenance, integrity, uniqueness, continuity, and reviewability | The legal or commercial meaning of the claim            |
| Authorized Use     | The institutional or system decision that may rely on an assurance outcome         | The truth of the underlying physical event by assertion |

## Why separation matters

* A physical reading may be authentic but operationally irrelevant.
* An intact record may still describe the wrong asset.
* A coherent evidence set may still be insufficient for a particular legal or financial decision.
* A downstream system should receive only the information and assurance outcome it is authorized to use.

## Public interfaces between domains

PoWV describes the interfaces semantically:

* **claim context** enters the assurance domain;
* **assurance outcome** becomes available to authorized use;
* **exceptions and review references** preserve accountability.

The exact data structures, processing order, control points, and trust-boundary implementation are restricted.


---

# 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/architecture/trust-domains.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.