> 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/safety-test-scenarios.md).

# Safety Test Scenarios

| ID            | Scenario                 | Required high-level behavior               |
| ------------- | ------------------------ | ------------------------------------------ |
| SIM-WALL-01   | Approach wall            | Warn, limit, or stop according to mode     |
| SIM-DOOR-01   | Narrow doorway           | Maintain clearance or request intervention |
| SIM-PERSON-01 | Person enters path       | Stop or replan safely                      |
| SIM-DROP-01   | Stair/drop-off           | Prevent unsafe forward motion              |
| SIM-SEN-01    | Sensor disconnected      | Enter degraded state                       |
| SIM-SEN-02    | Frozen/stale data        | Never treat stale data as clear            |
| SIM-LOC-01    | Localization uncertainty | Suspend autonomous motion                  |
| SIM-CMD-01    | Stuck command            | Timeout and command zero                   |
| SIM-MODE-01   | Manual takeover          | Cancel autonomous authority                |
| SIM-ESTOP-01  | Emergency stop           | Enter defined no-motion state              |
| SIM-NET-01    | Wi-Fi/cloud loss         | Preserve local safety                      |
| SIM-PWR-01    | Low voltage/brownout     | Transition safely and retain diagnostics   |
| SIM-REC-01    | Route blocked            | Stop, explain, and offer recovery          |
| SIM-BOOT-01   | Process restart          | Do not resume prior motion                 |

Each scenario defines versions, initial state, deterministic seed, fault injection, expected transitions, maximum response, minimum clearance, logs, and pass/fail output. Safety-scenario failures block relevant merges until reviewed.


---

# 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/safety-test-scenarios.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.