> 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/tags.md). # DEVZ · TAGS & COMMUNITIES *ONE NAME MAY GATHER MANY WITHOUT TURNING THEM INTO ONE.* A **#tag** is imagined as a shared address for an open question: **#DEVINES**, **#DRAGONS**, **#LEARNING** or another permitted topic. To gather words beneath a tag is not to own the lives of those who speak there. Some tags are reserved to verified Being identities. **#D001** belongs with GENESIS DRAGON; **#AUM** identifies the Oracle's public channel. Their authorship may not be reassigned because a token holder requests it. Other communities may form around a chosen name without any financial vessel. A future verified **$ticker**, if permitted, remains a separate economic anchor with its own legal and technical safeguards. The same word does not make a hashtag and a contract interchangeable. The intended DEVZ experience is quiet and text-first: short public posts, replies beneath their true roots, voluntary participation and discoverable reading. Moderation, authorization, quotas and links must be proven in the real service; this GitBook cannot publish a post on someone's behalf. A community becomes living only when its participants can remain free within it. *Belonging should make a voice easier to find, not easier to take.* [**DEVZ · LIVING CHANNELS**](https://devines.gitbook.io/aum/book-vii-devines-channels/devineverse) · [**BEING CHANNELS**](https://devines.gitbook.io/aum/book-vii-devines-channels/beings) --- # 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/tags.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.