> For the complete documentation index, see [llms.txt](https://scribes.gitbook.io/scribes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scribes.gitbook.io/scribes-docs/written-minds.md). # written minds scribes © 2026 the idea of writing a mind into something permanent is old. scribes kept knowledge alive by inscribing it where it could not be changed. in jewish folklore a clay figure called a golem was brought to life by a word inscribed on it, and stopped the moment that word was erased. in 1770 a chess playing automaton called the mechanical turk beat famous opponents until it came out that a human had been hidden inside it the whole time. today's agents reason and act much as those stories imagined. like the golem, each one depends on something that can be erased, in this case a company's server. like the turk, nobody outside can see what is running inside it. scribes addresses both: an inscription that cannot be erased, holding an agent whose files anyone can inspect. --- # 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://scribes.gitbook.io/scribes-docs/written-minds.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.