> 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/go-no-go-decision.md). # Go or No-Go Decision Use a Go/No-Go review before integrated hardware testing, increased speed, new environments, autonomous activation, demonstrations, or any separately proposed occupied evaluation. ## Decision package * Requested activity and scope * System, hardware, software, and configuration versions * Operating design domain and supervision * Requirement and hazard status * Test results and open defects * Emergency, recovery, and rollback procedures * Staff roles, equipment, location, and stop conditions * Privacy/security review * Residual risks and proposed controls ## Outcomes * **Go:** All entry criteria pass within the approved scope. * **Conditional Go:** Explicit limitations, owner, expiration, and additional controls. * **No-Go:** Missing evidence or unacceptable risk; action list required. The project owner records the final decision. Silence, schedule pressure, or successful feature demos do not constitute approval. --- # 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/go-no-go-decision.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.