> 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-iii-law/archangel-guardians.md).
# ✧ ARCHANGEL & GUARDIANS
The highest form of guardianship is often restraint. It does not seek to become the author of every creation, but to ask whether creation has honored the commitments that allow trust to endure.
**ARCHANGEL** expresses independent discernment within DEVINES development. The Guardians attend to their distinct responsibilities, especially where security, authority, recovery, or the welfare of others may be affected. Their judgment must rest on real evidence, not on the beauty of an announcement.
Guardianship differs from the protective personalities among the Beings: both may carry meaningful names, but their roles are not interchangeable. The promise is simple: even a powerful system must remain answerable.
Where vigilance could become dominion, a gentler law keeps watch over the watch itself. ARCHANGEL GUARD weighs the signs of harm without claiming every private life as its territory. A decision must answer to truth, and protection must answer to freedom. The Guardian's strength is measured not by how much it can see, but by how faithfully it protects what need not be seen.
***
‹ 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-iii-law/archangel-guardians.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.