> 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/for-builders/loader-and-runtime.md). # loader and runtime scribes © 2026 ### the loader the loader is a small program, inscribed on solana itself and shared by every scribe. when someone opens a scribe, the loader: 1. reads the birth transaction and the manifest 2. fetches every piece from the chain 3. checks each file against its hash and stops on any mismatch 4. assembles the files 5. starts the runtime in the visitor's browser the scribes platform caches pieces so scribes load faster. everything in the cache can be rebuilt from the chain. ### the runtime the runtime runs the model in webassembly and drives the agent loop: read the personality, think, pick a tool, use it, and repeat until the task is done. the settings are deterministic, so the same input always gives the same output. that is how anyone can reproduce a reply. ### tools in the browser * tools run in the visitor's browser. * tools cannot hold secrets, because everything inscribed is public. * any action that spends money needs approval from the visitor's own wallet. nothing is signed automatically. --- # 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/for-builders/loader-and-runtime.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.