> 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 vision behind a verifiable internet for AI — leveraging the synergies of crypto, internet, and AI technologies.

## 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).

### 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.origintrail.io/general/whitepaper-and-rfcs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.