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

# Glossary

Words you'll see in RAIDScout, in plain language. For the exact names of buttons and tabs, see [Terminology](https://docs.raidrobotics.org/raidscout/reference/terminology.md).

| Term             | Meaning                                                                                                                         |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Alliance         | Three teams that play a match together, red or blue. At alliance selection, eight captains each pick partners for the playoffs. |
| Audit            | The check of our scouting against the official scores and Match13, used to find entries to rescout.                             |
| Bank             | The teams on a pick board that aren't in a tier yet.                                                                            |
| Best             | The most points a team has scored in one match.                                                                                 |
| Breakdowns       | The share of a team's matches where its robot broke down.                                                                       |
| Calculated value | A number made from the form's questions, like all the teleop coral levels added up.                                             |
| Event phase      | Where the event is: pre-scouting, pits, or matches. It decides what Home and Scout show first.                                  |
| Floor            | What a team scores in a bad match: three out of four of their matches were better than this.                                    |
| Form             | A team's last 4 matches compared with its average. Up means they're improving.                                                  |
| Match13          | An outside site that rates every team. We use its xP and match forecasts.                                                       |
| Not a fit        | A team the drive coach thinks won't work with us. It stays off the tiers.                                                       |
| Overlap          | How much a team scores the same way we do. Lower means they add something we don't.                                             |
| Pick Priorities  | The weights strategists set for what matters in a partner. They rank every team and fill the team list.                         |
| Pit scouting     | Visiting a team's pit to ask about their robot.                                                                                 |
| Pre-scouting     | Notes on a team from videos and past events, before the event.                                                                  |
| Rescout          | Scouting a robot again from the match video because its entry looked wrong. The new entry replaces the old one.                 |
| Sorting Games    | Quick games (Compare, Rank) where everyone's answers build one rating per team.                                                 |
| TBA              | The Blue Alliance: where the schedule, scores and rankings come from.                                                           |
| Team list        | The one pick list used at alliance selection, built by the strategists.                                                         |
| Tier             | A group on a pick board: Tier 1 (first pick), Tier 2 (second pick), Tier 3 (backups).                                           |
| With us          | Our average points per match plus theirs.                                                                                       |
| xP               | Expected points: how many points Match13 predicts a team scores in a match.                                                     |


---

# 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/raidscout/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.
