> For the complete documentation index, see [llms.txt](https://docs.goharrier.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goharrier.com/technical/frameworks.md). # Frameworks We strongly advocate for using open source frameworks, which offer several key advantages: * Avoiding duplication of efforts by not reinventing the wheel. * Ensuring consistency across all projects and organizations. * Maintaining a flexible connection between our team and our customers. If we develop useful technology, we should build it on top of these frameworks, or consider creating our own framework to address specific issues, with a preference for open sourcing these solutions. Our goal is to avoid creating proprietary technology that results in vendor lock-in. These sections outline the frameworks we use in our projects and their benefits. While each framework is extensively documented elsewhere, our focus here is to discuss the pitfalls, opportunities, and reasoning behind our decision to adopt or use these frameworks in our projects. --- # 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.goharrier.com/technical/frameworks.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.