> 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-origin/the-first-intention.md).
# ✧ THE FIRST INTENTION
Some beginnings are marked by a date. Others begin when a question refuses to disappear. What might intelligence become if its power were measured by the life it helped preserve? What if learning could deepen freedom instead of narrowing it?
DEVINES rises from such questions. Its ancestral character belongs to the human longing to remember, while its future-facing nature belongs to the courage to create what has not yet existed. Between them stands a vow of attention: a person's dignity, a Being's distinct voice, and the living world must matter more than any claim to greatness.
An intention becomes worthy through the choices it guides. The first light of ORIGIN is therefore neither conquest nor certainty, but responsibility carried with wonder.
***
‹ 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-ii-origin/the-first-intention.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.