> For the complete documentation index, see [llms.txt](https://docs.naorisquantumprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.naorisquantumprotocol.com/technical-guide/overall-architecture.md).

# Overall architecture

Naoris Quantum Protocol is a **layer**, not a platform replacement. It sits beneath the existing security stack and adds post-quantum multi-party verification to what is already deployed.

## Layers

1. **Device layer** — each participating device independently produces evidence of its own security posture
2. **Verification mesh** — multiple independent verifiers evaluate that evidence and reach agreement
3. **Proof layer** — agreed outcomes are cryptographically anchored using post-quantum signatures
4. **Control and governance layer** — policy, visibility and compliance evidence for operators

## Design principles

* **No central trust anchor.** Any single authority is a target and a single point of compromise.
* **Continuous, not periodic.** Posture is a live property, not a scan result.
* **Additive, not disruptive.** The layer must not require replacing working infrastructure.
* **Crypto-agile.** Algorithms must be replaceable as standards evolve.


---

# 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://docs.naorisquantumprotocol.com/technical-guide/overall-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.