> 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/reference/certainty.md).

# How sure a value is

Every value in RAIDSystems shows how sure we are of it.

| Shown as  | Means                                                                                      |
| --------- | ------------------------------------------------------------------------------------------ |
| **18**    | Confirmed: two people agree, someone checked it on the robot, or the bus check measured it |
| **12/14** | One of two: two identical devices, and we don't know which is which                        |
| **13?**   | Not sure: one unchecked source, like the code, a spreadsheet or one note                   |
| **?**     | Not recorded                                                                               |

Every note keeps who recorded it and when, and notes are never edited, only replaced, approved or rejected. A note that disagrees with a confirmed value waits for a mentor. Everything still to check is on [Open items](https://docs.raidrobotics.org/raidsystems/robot/open-items.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/raidsystems/reference/certainty.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.
