> For the complete documentation index, see [llms.txt](https://wp.rebellionprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.rebellionprotocol.com/executive-summary/the-rebellion-community.md). # The Rebellion Community This project not only aims to become a success story, but it seeks to inspire a new generation of community driven projects. Our community is strong, knowledgeable and competent. It is composed of individuals who seek to become better everyday, to be part of something bigger and to contribute each individually to the greater cause. We are built upon a common purpose, a vision for the future, a mission to be fulfilled, as well as thousands of collective experiences that shape us along the way, and make our community an ever-evolving beast. We are a rebellion; a rebellion against the status quo, against the classical financial system, who is often too far from certain realities and not accessible to most of us. We are rebels, each in our own way. We are together to break frontiers, to build great things, we have no limits, we push forward until we succeed and prove the world that there is a new way to do things, a better way. Together we are strong, together we are one and together we are Rebellion. --- # 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://wp.rebellionprotocol.com/executive-summary/the-rebellion-community.md?ask=&goal= ``` `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.