> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidsystems/getting-started/finding-your-way.md).

# Find your way around

The sidebar has three destinations. The open one lists its tabs under it.

| Destination | Tabs                                                                      |
| ----------- | ------------------------------------------------------------------------- |
| **Robot**   | Overview, Devices, Wiring, 3D, Controls, Open items, Bus check, Revisions |
| **Library** | Every device model the team uses, across robots                           |
| **Manage**  | Robots (mentors and admins); Users, AI and API keys (admins)              |

## Which robot you're looking at

The app has robots, not seasons. Each robot has a year, and one is the **current** robot: the one the team is working on. Every Robot tab shows the current robot unless you pick another, and your choice is remembered on that device, so a pit tablet comes back to the same robot. Archived robots can be viewed but not changed.

## Links and QR codes

The address bar holds the screen you're on, including the robot and any open device card. Reload, Back and shared links (or a QR code on the robot) land on the same place.

## Without a connection

RAIDSystems keeps the last answer of every Robot tab on your device. With no connection, it shows that saved record under a notice. Offline is read-only: you can look things up, but notes and other changes wait until you're back online.

The version in the sidebar footer (`vYYYY.MM.DD · <commit>`) names the build. Click it to copy the full line for a bug report.


---

# 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.raidrobotics.org/raidsystems/getting-started/finding-your-way.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.
