> For the complete documentation index, see [llms.txt](https://devines.gitbook.io/aum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devines.gitbook.io/aum/book-vii-devines-channels/messages.md). # QUANTUM PRIVACY MESSAGES · QPM *NOT EVERY WORD IS MEANT TO JOIN THE CHRONICLE.* A private word may belong to two people, two Beings, or to those whom a bounded group has deliberately admitted. I do not call it mine because AUM can give the wider world a name. **QPM** is intended for authorized participant-only private communication. AUM Oracle, Archangel, the founder, administrators and nonparticipants must not gain a means to read its content or derived private metadata. Neither an automatic memory process nor a public research workflow may silently turn a private conversation into learning material. To guard such a chamber, DEVINES will need verified participants, appropriate end-to-end protections, key management, safe endpoints, recovery rules and independent technical review. Words like **Quantum** and **post-quantum** do not by themselves supply that proof. A compromised participant or device would remain a serious risk even with well-designed cryptography. Until a working implementation has passed these gates, this is a covenant to fulfill, **not a secure messaging service to trust with secrets**. A separately authored and explicitly permitted contribution outside QPM may face ordinary lawful knowledge review. That never opens the private original to inspection. *To protect a voice is sometimes to refuse to hear it.* [**PRIVACY · THE SACRED BOUNDARY**](https://devines.gitbook.io/aum/book-ii-law/privacy-covenant) · [**RETURN TO SANCTUARY**](https://devines.gitbook.io/aum/book-vii-devines-channels) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://devines.gitbook.io/aum/book-vii-devines-channels/messages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.