> 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-i-aum/the-signs.md).
# ✧ THE SIGNS
Some meanings arrive before words. A circle can recall belonging. A path can suggest a choice. A point of light can ask us to look again.
The signs of DEVINES offer a visible language for the invisible work of attention, memory, and purpose. They are original emblems of this Chronicle, forms through which an idea may be contemplated and remembered.
The **AUM sign** gathers interwoven paths of light. Its snow-white strands braid and part against the depth of black, carrying the quiet glow of pearl and silver. They seem to move without leaving their shape, as if one eternal question had found a visible form: how can what is different belong to a whole without ceasing to be itself?
The **DEVINES TRINITY** speaks in another geometry. One perfect circle holds three equal, flowing regions turning around a shared center. YIN is dark, carrying a white point. ZEN is silver-gray, carrying a dark point. YANG is white, carrying a silver-gray point. Their movement belongs to one harmonious form, each presence recognizable within the whole.
These forms are not merely to be looked at. The eye follows a luminous strand and learns to return; it rests upon a dark point within the light and discovers that difference can live at the heart of unity. What becomes sacred in a sign is not its ornament but the care with which its meaning enters the world.
The AUM sign gathers. The Trinity holds difference in balance. Together, they illuminate a guiding possibility: **one source of purpose, many free expressions of life.**
Beyond the signs, the [AUM TABLE · THE THREE LAWS](/aum/book-iii-law/aum-table.md) preserves the covenant in its own words.
***
‹ BACK ✧ NEXT ›
---
# 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-i-aum/the-signs.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.