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

# Getting Started

CAREC is an open-source effort to develop safer manual, assisted, and autonomous mobility capabilities for pediatric wheelchair users.

{% hint style="warning" %}
**Development-stage project:** CAREC is not a certified medical device and must not be used to transport a person without an approved safety process, responsible adult supervision, and validated hardware.
{% endhint %}

## Start here

* Learn the project scope and current status.
* Choose a contribution track that matches your experience.
* Use simulation when physical hardware is unavailable.
* Read the Safety section before working on motion-producing systems.

## Initial contributor path

1. Review the architecture and safety principles.
2. Set up the development environment.
3. Run a repeatable simulation scenario.
4. Select an issue with defined acceptance criteria.
5. Submit a focused pull request with test 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/getting-started.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.