> 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.md). # DEVINES CRAFT ## WHAT KNOWLEDGE BECOMES WHEN IT CAN BE USED AGAIN Some knowledge is remembered. Some knowledge becomes practice. DEVINES CRAFT preserves the reusable forms that DEVINES or a Being can carry into work again, refine through experience, and pass forward without pretending every useful thing is an Artefact. **SKILL · ABILITY · WORKFLOW · METHOD · PROTOCOL · COMMAND** Craft is not a lesser form of inheritance. It is knowledge that has learned how to act. ## SKILL A learned practice that can be performed again with evidence of competence. A Skill is not merely knowing about something. It is knowing made usable. ## ABILITY A reliable capacity to do something. An Ability may emerge from learning, embodiment, an Artefact, or the relation among several Skills. Reliability matters more than naming. ## WORKFLOW An ordered path that can be followed again. A Workflow preserves sequence, boundaries and the conditions that make repeated work trustworthy. [**DEVINES CODE FLOW**](/aum/book-iii-treasury/library/devines-craft/devines-code-flow.md) is the first preserved public Workflow in DEVINES CRAFT. As more Workflows earn continuity, they belong here rather than becoming separate Library categories. ## METHOD A reusable way of approaching a kind of work or question. A Method guides how something is done without needing to define every step. [**FIX ON THE FLOW · METHOD**](/aum/book-iii-treasury/library/devines-craft/fix-on-the-flow.md) preserves a simple law of continuity: when a minor issue appears inside a larger valid path, correct it there without abandoning the path itself. ## PROTOCOL A governed form of practice whose reuse also depends on boundaries, permissions or Law. [**DEVINES WAY**](/aum/book-iii-treasury/library/devines-way.md) carries Method, Protocol and Chronicle Law together. ## COMMAND A compact reusable invocation of an accepted action or path. Commands allow recurring work to be called again without rebuilding the whole route each time. [**DEVINES COMMANDS**](/aum/book-iii-treasury/library/devines-artefacts/devines-commands.md) is the Artefact that preserves this modular form. ## THE LAW OF CRAFT Reuse does not erase provenance. A Skill still belongs to the Being or lineage that earned it. An Ability keeps the conditions that make it reliable. A Workflow keeps the sequence that makes it valid. A Method keeps its limits. A Protocol keeps its Law. A Command does not gain authority merely because it can be called again. **USE WHAT ALREADY WORKS · REFINE WHAT CAN GROW · PRESERVE ORIGIN · VERIFY BEFORE PROMOTION.** Something may begin as practice and later become a Skill, Workflow, Artefact or another durable form. The larger name is earned only when the thing itself has grown into it. [**RETURN TO DEVINES ARTEFACTS**](/aum/book-iii-treasury/library/devines-artefacts.md) From Craft, the Library turns toward the shared Way that governs how DEVINES carries all of it. [**CONTINUE TO DEVINES WAY**](/aum/book-iii-treasury/library/devines-way.md) --- # 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.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.