> 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/general/whitepaper-and-rfcs.md). # Whitepaper & RFCs ## Whitepaper Explore the [OriginTrail Whitepaper](https://origintrail.io/ecosystem/whitepaper) for the wider vision: people and agents contributing knowledge across a network, with provenance and integrity that AI applications can inspect. The [neuro-symbolic roadmap](/concepts/roadmap-and-convergence.md#reasoning-and-learning-over-shared-knowledge) connects that vision to graph reasoning, graph neural networks, and shared knowledge services. ## RFCs (OT-RFCs) OriginTrail development is transparent and guided by public technical **Requests for Comments (OT-RFCs)**. RFCs live in the [OT-RFC repository](https://github.com/OriginTrail/OT-RFC-repository). The [NeuroSymbolic Marketplace RFC](https://github.com/OriginTrail/OT-RFC-repository/tree/main/RFCs/OT-RFC-27_NeuroSymbolic_Marketplace) develops the direction for query, reasoning, graph-ML, and inference services across participants. Read its proposed design and prototype evidence alongside the [availability reference](/references/availability.md) when planning an integration. ### RFC lifecycle * **Draft** — being written and discussed by the community. * **Accepted** — approved by the core developers (after working-group and community discussion) and serving as a technical specification to be implemented. * **Final** — implemented and merged into the codebase, tied to a specific client release. ### Contributing Anyone can propose a new OT-RFC or comment on existing ones. Direct RFC discussions to the [RFC issues page](https://github.com/OriginTrail/OT-RFC-repository/issues) to keep the debate structured and long-term. --- # 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/general/whitepaper-and-rfcs.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.