> For the complete documentation index, see [llms.txt](https://docs.overmind.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overmind.xyz/principles/philosophy.md). # Philosophy Overmind strives to be the following: * both accessible and challenging for developers of all levels * rewarding for users, intellectually and financially * a high-signal reference point for a developer's skill and creativity With those objectives in mind, Overmind quests are crafted according to the following principles: 1. **Self-contained**: require minimal context beyond the essential tools 2. **Creative**: require original thinking 3. **Unique**: have no close analogue available online 4. **Educational**: teach the user a new concept, method, or technique 5. **Applied**: relevant to real-world problems or applications Overmind quests are unlike most coding challenges, in that they take inspiration from problems developers encounter in the wild. Sorting a k-sorted array in O(n log k) is not a good challenge. Overmind quests are unlike most open source bounties, in that they have a low contextual barrier to entry. Users need not be familiar with a specific codebase or product in order to tackle them, therefore ramp-up time and effort are significantly lower. --- # 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.overmind.xyz/principles/philosophy.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.