> 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/raidparts/getting-started/glossary.md).

# Glossary

For the exact labels you see on screen, see [Terminology](/raidparts/reference/terminology.md).

| Term           | Meaning                                                                                                        |
| -------------- | -------------------------------------------------------------------------------------------------------------- |
| Assembly ready | Every live part is made, every COTS item is in stock, and everything is kitted.                                |
| BOM            | Bill of materials: the list of parts and subassemblies a subsystem needs.                                      |
| COTS           | Commercial off-the-shelf parts that we buy instead of make. Statuses: needed, ordered, received, in stock.     |
| Design part    | A part in the Design BOM. Numbered `YY-##A@@`, for example `26-01101`.                                         |
| Handoff        | When a designer clicks **Create part** on an approved design part, creating the part and its MO.               |
| Hold           | A pause while an admin decides. A held MO shows **On hold** and nobody works it.                               |
| Kitted         | Marked with **Kit**: the part or COTS item is gathered for assembly.                                           |
| MO             | Manufacturing order, numbered `MO-YY-####`. It carries a part through its stations.                            |
| Part           | The manufacturing part. Created by a designer from an approved design part.                                    |
| Problem        | A report on the MO's current step. It stays until an admin, or the person who reported it, clicks **Resolve**. |
| Rework         | After **QA fail…**, the MO is sent back to an earlier station and shows **Sent back by QA**.                   |
| Routing        | The ordered list of stations a part visits, generated from its type and options.                               |
| Season         | The build year. Only one is active at a time.                                                                  |
| Station        | Where work happens: Bandsaw, CAM, CNC Router, Bend, Debur, Coating, QA, Manual Lathe, Print, Post Process.     |
| Step           | One station's work on one MO: Pending, In progress, Complete.                                                  |
| Subassembly    | A numbered group of parts (1-9) within a subsystem.                                                            |
| Subsystem      | A section of the robot with a 2-digit code.                                                                    |


---

# 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/raidparts/getting-started/glossary.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.