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

# Roadmap

CAREC advances through evidence-gated simulation milestones before any future physical integration is considered.

## Current milestone — CAREC Sim 0.1

The current objective is a reproducible ROS 2 simulation in which contributors can:

1. launch a configurable digital wheelchair;
2. drive it manually;
3. record commands, pose, clearance, and interventions;
4. map and localize in deterministic indoor worlds;
5. navigate to predefined destinations;
6. enforce independent safety limits and emergency-stop behavior;
7. inject faults such as stale commands, sensor dropout, invalid localization, and invalid numeric input; and
8. produce machine-readable evidence with zero unsupported physical-safety claims.

## Current execution order

Interface ADR → ROS 2 workspace → digital wheelchair → virtual sensors → indoor worlds → teleoperation → safety supervisor → collision monitoring → fault injection → localization/navigation → shared control → dynamic-person benchmark → CAREC Sim 0.1 evidence report.

Physical wheelchair integration is outside the current milestone and requires separate requirements, ADRs, safety review, and evidence.


---

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