> 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.md).

# Safety

Safety is a system property, not a single sensor or algorithm. CAREC safety documentation defines assumptions, hazards, mitigations, evidence, and limitations.

{% hint style="danger" %}
CAREC documentation does not authorize clinical or unsupervised use. Performance targets and prototype results must never be represented as certified safety claims.
{% endhint %}

## Safety layers

1. Pre-use checks and a mandatory test sequence
2. Motion safety gate and bounded commands
3. Offline-capable obstacle warning and caregiver alerts
4. Independent manual override and emergency stop
5. Health monitoring, logging, and safe-state transitions

The CAREC concept deck proposes tiered proximity alerts and local processing. These remain design targets until validated through repeatable tests.


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.