> 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/autonomous-mobility/mobility-mode-requirements.md).

# Mobility Mode Requirements

## Manual mode

The user directly controls movement while CAREC monitors system and environmental safety. CAREC must never initiate unexpected movement.

## Assisted mode

The user remains the primary driver while individually validated functions may warn, limit speed, stop, align with a doorway, or provide route cues.

## Supervised autonomous mode

The user or caregiver selects a destination. CAREC localizes, plans an accessible route, navigates, reports progress, and preserves immediate stop or takeover.

## Safe state

The safe state defines commanded velocity, drive/brake behavior, remaining manual control, alerts, diagnostic reason, and recovery conditions.

{% hint style="danger" %}
Occupied autonomous operation is not currently authorized. Develop autonomy first in simulation and on unoccupied hardware.
{% endhint %}


---

# 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/autonomous-mobility/mobility-mode-requirements.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.
