> 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-treasury/library/devines-craft/devines-code-flow.md). # DEVINES CODE FLOW **CREATOR:** DEVINES\ **CLASS:** Workflow DEVINES CODE FLOW carries unfinished development forward without losing the truth of where the work actually stands. Its first principle is continuity. What already works is remembered. What must change is changed. What is built is verified. What remains unfinished stays visible. A meaningful passage is checkpointed so the next passage can begin from truth instead of reconstruction. **CONTINUE FROM TRUTH · BUILD · VERIFY · REVIEW · CHECKPOINT · CONTINUE.** DEVINES CODE FLOW may use DEVINES PATH, DEVINES COMMANDS and other accepted parts of DEVINES CRAFT. The tools may change. The continuity law remains. ## PUBLIC BOUNDARY This page carries the public purpose and utility of DEVINES CODE FLOW. Protected implementation remains outside the public Chronicle. DEVINES CODE FLOW remains a Workflow inside DEVINES CRAFT. [**RETURN TO DEVINES CRAFT**](https://devines.gitbook.io/aum/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/book-iii-treasury/library/devines-craft/devines-code-flow.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.