> 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/current-engineering-stack.md). # Current Engineering Stack CAREC currently develops a **simulation-first ROS 2 autonomous wheelchair stack**. ## Active * ROS 2 Jazzy interfaces and packages * configurable digital wheelchair model * Gazebo / `ros_gz` simulation * RViz2 visualization * manual and shared control * localization, mapping, and navigation * perception and sensor fusion * independent safety supervision * deterministic fault injection and scenario testing * machine-readable evaluation evidence ## Not part of CAREC Sim 0.1 * ESP-IDF or ESP32 development * SenseCAP Watcher or other device-specific firmware * cloud/mobile applications * physical wheelchair motor integration * claims of clinical, regulatory, or physical safety validation GitHub `main` is authoritative. GitHub Issues track work state. GitBook publishes approved documentation from `main`. --- # 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/current-engineering-stack.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.