> 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/roadmap/milestones-and-exit-criteria.md). # Milestones and Exit Criteria Every milestone names an owner, dependencies, deliverable, test environment, acceptance criteria, open risks, and decision authority. ## Foundation gate * System boundary and operating modes * Arbitration and safety-supervisor requirements * Hazard log, safe state, takeover, and emergency stop * Interface, privacy, and evidence rules ## Simulation gate * Version-pinned environment * Wheelchair geometry and dynamics * Manual control and drive feedback * Accessible worlds and sensor models * Fault injection and automated safety scenarios ## Assisted-safety gate * Perception and sensor-fusion evidence * Speed-aware collision response * Warning accessibility and caregiver behavior * Sensor-failure and degraded-state tests * Bounded intervention and takeover tests ## Hardware gate * Approved drive interface and isolation review * Independent stop and power removal * Secure mounting and protected power * Reliability, battery, and environmental evidence * Unoccupied bench and controlled-course results ## Autonomy gate * Localization uncertainty handling * Accessible routes and doorway clearance * Dynamic-obstacle and recovery behavior * Defined operating design domain * Goal success, intervention, clearance, and safe-stop metrics A feature can pass its own test while the complete platform remains unready. System progression requires integrated 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/roadmap/milestones-and-exit-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.