> 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/readme.md).

# RAIDSystems

RAIDSystems is the robot's electrical and programming schematic for FRC Team 4469: every device, CAN ID, PDH channel, IP address, wire and controller button, with how sure we are of each one. It answers "what is this device, where is it, and how is it wired and coded?" from a phone in the pit.

## Who this is for

| Role       | What you do                                                                   | Start here                                                                                          |
| ---------- | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Student    | Look things up, record what you see on the robot, run the bus check           | [Devices](https://docs.raidrobotics.org/raidsystems/robot/devices.md)                               |
| Programmer | Sync the robot code, fill in the device library                               | [Overview and code sync](https://docs.raidrobotics.org/raidsystems/robot/overview-and-code-sync.md) |
| Drive team | Approve what each controller button does                                      | [Controls](https://docs.raidrobotics.org/raidsystems/robot/controls.md)                             |
| Mentor     | Approve notes that disagree, assign open items, save revisions, manage robots | [Open items](https://docs.raidrobotics.org/raidsystems/robot/open-items.md)                         |
| Admin      | Users, roles, the current robot, AI and API keys                              | [Manage](https://docs.raidrobotics.org/raidsystems/manage/manage.md)                                |

New here? Start with [Sign in and get a role](https://docs.raidrobotics.org/raidsystems/getting-started/sign-in-and-access.md).

## How it fits with the other RAID apps

* **RAIDLogs** reads RAIDSystems' revisions so it can check each match against the robot as it was that day. See [Revisions](https://docs.raidrobotics.org/raidsystems/robot/revisions.md).
* **RAIDParts** tracks the robot's parts and manufacturing. RAIDSystems tracks its electrical and code side.


---

# 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/readme.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.
