> For the complete documentation index, see [llms.txt](https://www.projectpanoptes.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.projectpanoptes.org/build/getting-started.md).
# Start Building!
Ready to build a PANOPTES unit? Have a technical question about the setup? Curious about what that even means? This section is for you!
This section of the guide is the primary source for official build and installation instructions related to a PANOPTES unit.
Project PANOPTES provides instructions and a parts list for a complete PANOPTES unit. However, it's important to note that there are potentially many alternative ways to build various parts of the unit as long as the functional requirements are taken into consideration.
A good example would be specific weather proofing tips for weather at your site that might not be covered by the official guides. The functional requirements for weatherproofing are:
1. Don't let your PANOPTES unit get ruined by the weather (or bugs!)
2. Weatherproofing materials shot not interfere with the movement of the mount.
We offer a working solution on how to do that with specific tools and hardware, but as long as you are able to satisfy the functional requirements for each section, feel free to explore better (or cheaper!) options.
{% hint style="info" %}
Something unclear? Please post on the forum at or email us at .
{% endhint %}
---
# 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://www.projectpanoptes.org/build/getting-started.md?ask=&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.