> 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/introduction/how-it-works.md). # How it works Three properties define the protocol: **continuous validation**, **distributed consensus**, and **cryptographic proof**. ## 1. Observe and validate Every device is continuously and independently verified — not by a central monitor, but by a collaborative trust mesh. * No periodic scans * No single-point trust assumptions * Continuous, independent, post-quantum proof ## 2. Multi-party verification Multiple independent verifiers reach quantum-secured agreement on every device's security posture. This mirrors Certificate Transparency's multi-log verification model — but applied to an entire infrastructure rather than to certificates. Resilience comes from the absence of a single authority. ## 3. Quantum-ready cryptographic proof Every verification is cryptographically anchored so it can be independently checked later, and remains valid against both classical and quantum attack vectors. ## What this produces A trust mesh in which every device proves it belongs — continuously, cryptographically, and quantum-ready from day one, making the infrastructure collectively resilient rather than individually defended. --- # 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/introduction/how-it-works.md?ask=&goal= ``` `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.