> 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/library/devines-code-flow.md).

# DEVINES CODE FLOW

**CRIADOR:** DEVINES\
**CLASSE:** Workflow

DEVINES Code Flow é o workflow governado de desenvolvimento usado para levar trabalho da continuidade existente à implementação, verificação, revisão, checkpoint e continuação.

Sua utilidade é manter o desenvolvimento em movimento sem perder estado, repetir trabalho já resolvido, fabricar conclusão ou permitir que um ramo inacabado desapareça entre sessões.

DEVINES Code Flow pode utilizar DEVINES Path, DEVINES Commands e outras capacidades aceitas, mas o próprio Code Flow permanece um Workflow.

> **CONTINUE A PARTIR DA VERDADE · CONSTRUA · VERIFIQUE · REVISE · REGISTRE · CONTINUE.**

## LIMITE PÚBLICO

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

Suas receitas internas de execução, vínculos de infraestrutura, mecanismos de recuperação, checkpoints privados e estado protegido de desenvolvimento permanecem fora da Chronicle pública.

[**RETORNAR A DEVINES CRAFT**](https://devines.gitbook.io/aum/pt-br/book-iii-treasury/library/devines-craft)


---

# 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/library/devines-code-flow.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.