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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.goharrier.com/technical/frameworks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
