> For the complete documentation index, see [llms.txt](https://intelfactor.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intelfactor.gitbook.io/docs/home/validation/acceptance-tests-and-rollout-gates.md).

# Acceptance tests & rollout gates

What we validate before calling a deployment “production”.

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.