> 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/security/disclosure-boundary.md).

# Disclosure Boundary

What the public documentation explains and what remains restricted.

PoWV uses a controlled-disclosure model so the public can understand the protocol's purpose and assurance claims without receiving an implementation blueprint.

## Public

* problem definition and institutional thesis;
* assurance dimensions and design principles;
* capability-level architecture;
* threat classes and security objectives;
* deployment profiles;
* use-case patterns;
* maturity status and evaluation indicators.

## Controlled technical evaluation

May be shared with authorized parties under an appropriate confidentiality and review framework:

* deployment-specific requirements;
* evaluation methodology and selected test evidence;
* integration assumptions;
* security review material;
* partner-specific architecture.

## Restricted

* production firmware and source logic;
* exact event structures and serialization;
* cryptographic profiles and key-management procedures;
* device provisioning and attestation logic;
* internal trust boundaries and processing sequences;
* anti-replay, aggregation, anchoring, and recovery construction;
* hardware schematics, wiring, and industrial connector details;
* scoring weights, thresholds, test vectors, and benchmark datasets;
* credentials, customer data, and partner-specific configurations;
* economic-control formulas and settlement parameters.

{% hint style="danger" %}
Public availability of a file or repository does not automatically mean its contents are appropriate for institutional documentation. Publication decisions follow the disclosure classification above.
{% endhint %}


---

# 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/security/disclosure-boundary.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.