> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/getting-started/terminology-and-scope.md).

# Terminology and Scope

## Canonical definitions

* **CAREC:** Cognitive Autonomous Robotic Electric Chair—the complete manual, assisted, and autonomous wheelchair platform.
* **Forward collision-warning prototype:** The older SenseCAP-based obstacle-warning and caregiver-alert feature.
* **Manual mode:** User directly controls mobility.
* **Assisted mode:** User controls mobility while validated safety functions may intervene.
* **Supervised autonomous mode:** CAREC navigates to a selected goal while immediate human takeover remains available.
* **Safe state:** Defined system condition intended to reduce unacceptable risk.
* **Operating design domain:** Conditions under which a capability is intended and validated to operate.

{% hint style="warning" %}
The older approximately $200 estimate, camera targets, distance zones, and battery claims apply only to the historical collision-warning feature concept—not to the complete CAREC wheelchair.
{% endhint %}

New documents and public communications must preserve this distinction.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://carec.gitbook.io/carec-docs/documentation/getting-started/terminology-and-scope.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.