> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/archive/v9.md). # V9 Archive These pages are historical V9 material. They are preserved for audit, migration, and design archaeology only. Use the current V10 docs for install, agent connection, memory lifecycle, publishing, peer connectivity, and operational guidance.
SectionContains
OnboardingHistorical V9 walkthroughs for publish, query, agent lifecycle, and package layout.
SetupHistorical setup and testnet notes.
SpecsHistorical protocol and economics specs.
PlansHistorical implementation plans.
DiagramsHistorical flow diagrams.
Use casesHistorical V9 use-case notes.
Future ideasHistorical ideas that are not current V10 operating guidance.
MiscellaneousHistorical branch notes, feedback, and other archived material.
--- # 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://docs.origintrail.io/archive/v9.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.