> 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/development/development-environment.md). # Development Environment The development environment must be reproducible for contributors who have no wheelchair hardware. ## Baseline deliverables * Supported host operating systems and CPU architectures * Pinned ROS 2, simulator, compiler, Python, and tool versions * Dev container or scripted setup * Repository bootstrap and dependency verification * One-command build and test * Reference simulation world and sample run * Health-check command * Log and report output locations * Troubleshooting for common environment failures ## Setup verification A clean machine is considered ready only when it can: 1. Build the workspace 2. Launch the reference wheelchair simulation 3. Send a bounded manual command 4. Receive sensor and drive feedback 5. Execute an emergency-stop scenario 6. Run the CI test subset locally 7. Export a reproducible report Hardware-specific dependencies must remain optional and isolated behind adapters. --- # 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/development/development-environment.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.