> 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/safety/safe-states-and-manual-override.md). # Safe States and Manual Override Defined safe states, takeover, emergency stop, recovery, and restart behavior. A safe state is a complete system condition, not merely “software stopped.” ## Safe-state definition Specify authorized motion, drive-enable and brake state, available manual control, active health monitoring, user/caregiver status, logged reason, and recovery prerequisites. ## Manual takeover * Higher priority than autonomous planning * Cancels queued goals and future planner commands * Has a defined maximum latency * Remains available during noncritical autonomy faults * Produces visible confirmation and a log event * Is tested during motion, recovery, communication loss, and restart ## Recovery CAREC verifies required sensors, configuration, drive feedback, E-stop reset, and operator intent before leaving the safe state. Power restoration or application reconnection alone is never sufficient. --- # 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/safety/safe-states-and-manual-override.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.