> 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/operations/technology/applications.md).

# Applications

Every member uses the team's apps. Each one has a job, so you always know where to look.

| App                                                                                               | What we use it for                                                                                       | Who uses it                          |
| ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| [monday.com](https://docs.raidrobotics.org/operations/technology/applications/monday-overview.md) | Team tasks, attendance and meeting agendas                                                               | Everyone                             |
| Slack                                                                                             | Announcements and conversation. Team announcements during the season and at competitions go here         | Everyone                             |
| [RAID Docs](https://docs.raidrobotics.org)                                                        | How we do things: the handbook, subteam guides and app guides                                            | Everyone                             |
| [RAIDParts](https://parts.raidrobotics.org)                                                       | Robot parts, BOMs and manufacturing orders, from design to the shop floor                                | Design and build                     |
| [RAIDScout](https://docs.raidrobotics.org/raidscout)                                              | Scouting at events and building pick lists                                                               | Scouts and strategy                  |
| [RAIDSystems](https://docs.raidrobotics.org/raidsystems)                                          | The robot's electrical and code schematic: every device, CAN ID, PDH channel, wire and controller button | Electrical, programmers, drive team  |
| [RAIDLogs](https://docs.raidrobotics.org/raidlogs)                                                | Turning each match's robot logs into a list of things to check before the next match                     | Pit crew, programmers, drive coaches |

Rules for using these apps safely, including direct messages between students and adults, are in the Team Handbook under [Digital Safety](https://docs.raidrobotics.org/team-handbook/policies/safety/digital-safety.md).


---

# 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/operations/technology/applications.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.
