> 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/intended-use-and-limitations.md). # Intended Use and Current Limitations What CAREC is intended to explore and what is currently prohibited. ## Intended engineering use * Research and open-source development of wheelchair safety and autonomy * Simulation of manual, assisted, and autonomous mobility * Development of modular sensing, navigation, control, and human interfaces * Unoccupied prototype testing under documented procedures * Reproducible experiments, safety evidence, and contributor education ## Current limitations * Not a certified medical device * Not approved for occupied motion testing * No clinically validated autonomy or collision-avoidance performance * No finalized wheelchair drive interface or production sensor suite * No approved operating design domain * No authorization to make medical, safety-certification, or regulatory claims ## Prohibited interpretation Documentation, presentations, code, and demonstrations must not imply that experimental features are ready to transport a child or that a subsystem result proves whole-platform safety. --- # 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/intended-use-and-limitations.md?ask=&goal= ``` `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.