> 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/design/cad-standards/parts-of-a-robot.md).

# Parts of a Robot

This page will walk through the basic components that make up a full robot assembly from the top level down to the bottom

## Robot

There is always one robot. FRC is a competition where we compete with exactly one robot per competition. This one robot may change throughout the season leading to multiple versions with different components, but there will be one that we take to competition.

## Subsystem

A subsystem is a collection of mechanisms that work together to achieve a distinct and specific function towards the end goal of scoring points.

## Assembly

An assembly is a subset of parts and pieces that get put together before being merged into a subsystem. RAIDParts calls these subassemblies.

## Part

A part is an individual component, manufactured or purchased, that goes into the robot. Every part we make has a [part number](https://docs.raidrobotics.org/design/part-numbers-and-boms/part-numbers.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/design/cad-standards/parts-of-a-robot.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.
