# Acceptance tests & rollout gates

Rollout is engineering validation. It is not just ML metrics.

### Functional gates

1. **Local continuity:** run 24+ hours with connectivity loss (unplug ethernet).
2. **Evidence traceability:** random audit shows zero missing artifacts.
3. **Operator workflow:** usable on shift with Chinese-primary UI (if required).
4. **RCA loop complete:** defect → cause → action → operator response → triple stored.

### Performance gates

* Detection latency meets spec under production load.
* Throughput matches line speed with no sustained frame drops.
* 24-hour soak test with no memory leaks or queue growth.
* Recovery from disconnects, power cycles, and storage pressure.

### Security gates

* No corporate IT → camera network path.
* Remote access requires MFA and maintenance windows.
* If OPC UA is used: signing/encryption enabled (never “None”).
* Inference nodes generate no outbound internet traffic by default.


---

# Agent Instructions: 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:

```
GET https://intelfactor.gitbook.io/doc/home/validation/acceptance-tests-and-rollout-gates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.