> 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/simulation/simulator-acceptance-criteria.md). # Simulator Acceptance Criteria The shared baseline is accepted only when a new contributor can reproduce it from a clean machine. ## Required capabilities * Pinned ROS 2 and simulator versions * Scripted or containerized setup * Wheelchair geometry, dynamics, and control limits * Manual control, drive feedback, and emergency stop * Camera, odometry, IMU, and ranging/depth models * Indoor worlds with doors, ramps, obstacles, people, and drop-offs * Sensor dropout, stale data, latency, and network fault injection * Deterministic scenario seeds * Logs, replay, metrics, and machine-readable pass/fail * Continuous-integration execution for a safety subset A clean installation must build, launch the reference world, drive manually, run one navigation goal, execute an emergency-stop test, and export a report using documented commands. --- # 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/simulation/simulator-acceptance-criteria.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.