> For the complete documentation index, see [llms.txt](https://nextsearch.gitbook.io/next-proposal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nextsearch.gitbook.io/next-proposal/how-we-are-open/radically-open.md). # Radically Open We love open source. To be a consumer of a product/service with no leverage to encourage the producer to improve their offering can leave us feeling helpless and have a real negative effect upon quality of life. Open source provides us with leverage. Open source provides the ability to forge ahead even when the original producer refuses to do so. If you don't like the way an open source product/service is being offered, you can utilize the existing product to create something even better. This forces the original producer to either innovate to match/exceed the new offering or watch as their users (for good reason) leave for the better option. In the next several pages we will discuss specific ways in which we will be radically open which we believe will force us to be accountable to our consumers and thus spur constant innovation, humility, and responsiveness. --- # 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://nextsearch.gitbook.io/next-proposal/how-we-are-open/radically-open.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.