> 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/development/release-process.md).

# Release Process

CAREC releases are evidence packages, not only code tags.

## Release types

| Type                 | Purpose                               | Permitted use                       |
| -------------------- | ------------------------------------- | ----------------------------------- |
| Development snapshot | Integration and simulation            | Engineering only                    |
| Feature prototype    | Isolated hardware/software experiment | Unoccupied approved testing         |
| Integrated prototype | Multi-subsystem qualification         | Unoccupied controlled testing       |
| Evaluation candidate | Formal review package                 | Only under separately approved plan |

## Required release contents

* Versioned source, dependencies, configuration, and build instructions
* Supported hardware/simulator matrix
* Requirements and issues included
* Test summary and linked raw artifacts
* Safety impact and hazard-log changes
* Known limitations and prohibited uses
* Upgrade, configuration migration, rollback, and recovery instructions
* Security/privacy notes
* Named owner and required approvals

## Release workflow

1. Freeze scope and candidate versions.
2. Run required CI, simulation, qualification, and documentation checks.
3. Review unresolved defects and residual risks.
4. Create the release notes and evidence index.
5. Obtain owner-controlled approval for safety-relevant or public releases.
6. Publish, verify download/install, and monitor early failures.
7. Roll back or withdraw if release criteria are violated.

No release label should imply clinical readiness, certification, or occupied-use authorization.


---

# 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/development/release-process.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.