| Mandatory gate | Evidence needed | Result if unresolved |
|---|---|---|
| Authority to process the data | Approved document use and complete data path | No confidential uploads |
| Accountable release | Named technical/commercial approvers and demonstrated permissions | No live quotation or price update |
| Critical scope handling | Agreed test outcomes; no unresolved critical failure in the accepted holdout set | Remediate and retest |
| Source and revision integrity | Material outputs traceable to the correct issue | No acceptance of the affected task |
| Recoverable live integration, if included | Failed/duplicate transfer, reconciliation and recovery demonstrated | Remain offline or in sandbox |
| Sustainable operation | Named owner, support and usable exit output | No routine production release |
The critical-failure gate is a proposed acceptance policy for the tested sample, not a statistical guarantee that future errors cannot occur. A gate marked “not applicable” needs a documented scope reason; it must not be used to hide an essential requirement.
Sources cited on this page
No external sources are cited on this page. Every source for this section is listed on its Sources page.