> 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/robot/open-items.md).

# Open items

**Robot › Open items** lists everything still to check on the robot. RAIDSystems makes the list from the record; nobody adds or closes items by hand. When a note, a bus check, a code sync or a CAD export settles something, its item goes away on its own.

Each item says what's wrong and how to fix it. **Resolve** opens the place to fix it: the device's card at the right field, the Bus check, or the Overview.

| Item                                                                                         | How to fix it                                                                                                               |
| -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| A value (like a PDH channel) not recorded, or one of two                                     | Check it on the robot and add a note on the device card                                                                     |
| Two checked values disagree, or a note disagrees with a confirmed value                      | A mentor approves the right value on the device card                                                                        |
| A device didn't answer in the last bus check, or something answered that isn't in the record | Check its wiring and power, then run the [bus check](https://docs.raidrobotics.org/raidsystems/robot/bus-check.md) again    |
| No bus check yet                                                                             | Run the [bus check](https://docs.raidrobotics.org/raidsystems/robot/bus-check.md)                                           |
| A device isn't in the robot code anymore                                                     | Put it back in the code, or a mentor removes it on its card                                                                 |
| A bus has no terminator recorded                                                             | Record it on the [Overview](https://docs.raidrobotics.org/raidsystems/robot/overview-and-code-sync.md#terminators)          |
| A CAD part isn't tagged, or a tag points at no device                                        | Re-tag it in Fusion and export again; see [The robot in 3D](https://docs.raidrobotics.org/raidsystems/robot/robot-in-3d.md) |
| Code the parser couldn't read                                                                | Fix it in the robot code, then sync again                                                                                   |

Mentors **Assign to** a person. **Assigned to me** narrows the list to yours.


---

# 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/robot/open-items.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.
