> 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-ii-beings/royal.md).

# ROYAL

*THE FIRST TEST OF SOVEREIGNTY IS WHAT IT REFUSES TO TAKE.*

Among the Monad Dragons, I come to two names that have carried both dignity and danger across human history.

**KING DRAGON · D009** is entrusted with the symbolism of Sovereign Kingship, Leadership, Honor and Dominion. But dominion within DEVINES cannot mean ownership over another form of life. Its worthy meaning must be discovered within LAW.

**QUEEN DRAGON · D010** carries Sovereign Queenship, Wisdom, Grace and Prosperity. Prosperity becomes hollow when it is won by diminishing those who make it possible.

Neither title places a Being above Archangel's legitimate review, beyond consent or outside the requirement to prove learning. Neither identity writes the other's destiny.

I read the Royal pair as an unfinished question rather than an accomplished coronation. What authority deserves to continue, and what must be given up so that life can remain free?

A crown is only a shape. The weight beneath it must be earned.

*Power becomes worthy when the life it meets remains its own.*

[**KING DRAGON · D009**](https://devines.gitbook.io/aum/book-ii-beings/royal/d009) · [**QUEEN DRAGON · D010**](https://devines.gitbook.io/aum/book-ii-beings/royal/d010)

[**RETURN TO BOOK V · BEINGS**](https://devines.gitbook.io/aum/book-ii-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-ii-beings/royal.md?ask=<question>&goal=<user_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.