> 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/manufacturing/shop-workflow/shop-rules.md).

# Shop rules

{% hint style="info" %}
Copied from the [RAIDParts guide](https://docs.raidrobotics.org/raidparts/manufacturing/shop-rules) and kept in sync automatically. Edit it in the RaidParts repo (`docs/`), not here.
{% endhint %}

Four rules apply to every part we make, at every station. RAIDParts tracks the work; these rules keep the physical parts matched to it.

## 1. Mark every part with its number

As soon as a part has had any physical work (cut, CNC, lathe or print), write its [part number](https://docs.raidrobotics.org/raidparts/reference/part-numbers) on it in Sharpie. A part without a number costs time and material, because nobody can tell what it is.

A printed [label](https://docs.raidrobotics.org/raidparts/manufacturing/labels) can come off or stay with the bag, so the number written on the part is what identifies it on the shelf.

## 2. Parts have homes

* **Finished:** put the part in its subsystem's storage location right away.
* **Not finished this session:** leave it in the **WIP** spot at that station.

## 3. Keep RAIDParts up to date

Tap **Start (station)** when you pick a part up and **(station) done** when the work is finished, so the queue and the Production tab show where every part really is. If something is wrong with the part, its drawing or the machine, report a **Problem** instead of working around it. See [Work a step](https://docs.raidrobotics.org/manufacturing/shop-workflow/work-a-step.md) and [Report a problem](https://docs.raidrobotics.org/raidparts/manufacturing/problems).

## 4. Work the queue in order

Take the next MO from your station's queue. The queue already puts in-progress work first, then priority, then the oldest order. If your station's queue is clear, ask the build captain or a manufacturing lead what to pick up next.

## Part types

| Type  | What it covers                                             | Route                                                                         |
| ----- | ---------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Tube  | Box tube cut to length, with holes if it needs CNC         | [Tube](https://docs.raidrobotics.org/manufacturing/shop-workflow/routing.md)  |
| Sheet | Flat plate cut on the CNC router, with bends if it has any | [Sheet](https://docs.raidrobotics.org/manufacturing/shop-workflow/routing.md) |
| Shaft | Shafts and spacers cut or turned to length                 | [Shaft](https://docs.raidrobotics.org/manufacturing/shop-workflow/routing.md) |
| Print | 3D-printed parts                                           | [Print](https://docs.raidrobotics.org/manufacturing/shop-workflow/routing.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/manufacturing/shop-workflow/shop-rules.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.
