> 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/pt-br/book-iii-treasury/devines-artefacts/devines-path.md).

# DEVINES PATH

**CRIADOR:** DEVINES\
**CLASSE:** Artefato DEVINES de caminho adaptativo

DEVINES Path ajuda DEVINES a escolher a rota válida mais forte para uma demanda específica sem reconstruir aquilo que já funciona.

Sua utilidade é reutilizar caminhos comprovados, combinar rotas modulares e criar uma nova ramificação apenas quando um caminho existente já não atende exatamente à necessidade.

Cada ramificação útil pode ser preservada e reutilizada depois, permitindo que DEVINES melhore pelo uso em vez de redescobrir repetidamente a mesma solução.

> **REUTILIZE O QUE FUNCIONA · RAMIFIQUE ONDE NECESSÁRIO · PRESERVE O QUE MELHORA O CAMINHO.**

## LIMITE PÚBLICO

Esta página descreve apenas o propósito e a utilidade de DEVINES Path.

Seu registro interno de ramificações, regras de execução, caminhos de infraestrutura, vínculos de comandos e lógica operacional protegida permanecem fora da Chronicle pública.


---

# 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/pt-br/book-iii-treasury/devines-artefacts/devines-path.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.