> 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.md).

# Architecture

A non-normative public architecture for physical context, evidence assurance, and authorized use.

PoWV is organized as a modular assurance framework for connecting physical claims with authorized digital use.

![PoWV public trust architecture](https://1151534167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWO75canbSRCuzukBrP8n%2Fuploads%2FNolNPZEKfr2SbRS4CSx5%2Fpublic-trust-architecture.svg?alt=media)

{% hint style="info" %}
This diagram is a non-normative capability view. It does not represent firmware execution order, network topology, or an implementation specification.
{% endhint %}

## Three public trust domains

| Domain             | Core question                                                                                                          | Public outcome                                                          |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Physical Context   | What real-world asset, event, measurement, location, or custody relationship is being claimed?                         | A bounded claim that can be evaluated                                   |
| Evidence Assurance | Can the claim be attributed, checked for integrity, distinguished from conflicting claims, and independently reviewed? | A defensible evidence position                                          |
| Authorized Use     | Which approved system or institution may rely on the result, and for what purpose?                                     | Audit, compliance, insurance, finance, reporting, or settlement support |

## Architectural characteristics

* **Modular:** deployment context can change without redefining the protocol's public assurance objectives.
* **Evidence-centered:** the system evaluates support for a claim rather than accepting an assertion as truth.
* **Multi-signal:** stronger confidence may be constructed from complementary evidence sources; no single signal is assumed to be sufficient in every deployment.
* **Reviewable:** an authorized reviewer should be able to understand why a claim was accepted, rejected, or routed for exception handling.
* **Connectivity-aware:** the assurance model is designed for both connected and constrained operating environments.
* **Controlled-disclosure:** public documentation explains capabilities while implementation-critical material remains restricted.

## Explore this architecture

* [Trust Domains](/powv-protocol-docs/architecture/trust-domains.md)
* [Design Principles](/powv-protocol-docs/architecture/design-principles.md)
* [Deployment Profiles](/powv-protocol-docs/architecture/deployment-profiles.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/architecture.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.