> 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/verification-and-validation.md).

# Verification and Validation

Verification asks whether CAREC meets written requirements. Validation asks whether the resulting behavior is suitable for its intended environment and users. Both apply to the complete integrated system.

## Evidence ladder

1. Static analysis and unit tests
2. Component integration and software-in-the-loop
3. Repeatable simulation and fault injection
4. Hardware-in-the-loop
5. Unoccupied bench testing
6. Unoccupied controlled-course testing
7. Reliability and environmental qualification
8. Only then, separately approved evaluation planning

## Core evidence

| Area              | Required evidence                                         |
| ----------------- | --------------------------------------------------------- |
| Modes and control | Transition, priority, timeout, takeover, restart          |
| Safety supervisor | Limits, vetoes, safe states, reason codes                 |
| Drive interface   | Range, rate, feedback, faults, isolation                  |
| Perception        | False negatives, false positives, latency, uncertainty    |
| Localization      | Error, loss detection, relocalization                     |
| Navigation        | Clearance, route compliance, recovery, intervention       |
| Sensors           | Disconnect, obstruction, stale/frozen/corrupt data        |
| Power             | Brownout, shutdown, low battery, recovery                 |
| Reliability       | Repeated power cycles and extended burn-in                |
| Interfaces        | Accessibility, confirmation, cancellation, caregiver loss |
| Security/privacy  | Update integrity, secrets, logs, data minimization        |

Initial prototype qualification may include 100 power cycles and a 72-hour burn-in, but these engineering thresholds are not a substitute for clinical, regulatory, or medical-device validation.

Every result records system version, configuration, environment, sample size, raw artifacts, analysis, owner, date, limitations, and requirement links.


---

# 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/verification-and-validation.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.