> 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/deployment-profiles.md).

# Deployment Profiles

Public profiles for fixed, mobile, remote, and hybrid PoWV environments.

Deployment profiles describe operating conditions without prescribing proprietary hardware or software.

| Profile           | Operating context                          | Assurance emphasis                              | Typical constraint                |
| ----------------- | ------------------------------------------ | ----------------------------------------------- | --------------------------------- |
| Fixed Site        | Industrial or warehouse environment        | Stable provenance and repeatable review         | Legacy integration                |
| Corridor          | Road, rail, or multimodal movement         | Custody continuity and exception visibility     | Multiple organizations            |
| Remote            | Sparse or intermittent connectivity        | Evidence durability and reconciliation          | Limited bandwidth or availability |
| Mobile Field      | Human-operated collection or inspection    | Context completeness and accountable submission | Variable devices and conditions   |
| Enterprise Hybrid | Existing operational and financial systems | Interoperability and controlled disclosure      | Heterogeneous data governance     |

## Profile selection

A deployment profile is selected by risk, evidence policy, infrastructure constraints, authorized stakeholders, and the consequence of accepting an unsupported claim.

Profiles are not product SKUs and do not disclose internal topology. They are a public vocabulary for discussing deployment requirements.


---

# 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/deployment-profiles.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.