Hardware-in-the-Loop Revalidation Before Return-to-Service
Objective
Ensure systems involved in an incident undergo physical HITL revalidation, not merely software review, before returning to operation.
Control / requirement
Mandatory HITL test pass tied to root-cause-specific scenarios before reactivation.
Applicability
Any physical AI system involved in an incident requiring containment or recovery.
Expected evidence
Revalidation test records; root-cause traceability. [T2/T3]
Assurance expectation
Evidence that revalidation scenarios specifically target the identified root cause, not a generic pre-deployment test suite.
Dependencies
PAI-SF-TST-001 (Domain 10, HITL testing methodology) — same testing capability, incident-driven trigger and scope here rather than pre-deployment.
Exclusions
Not applicable to incidents with no plausible physical root cause (e.g., purely administrative/governance incidents).
Maturity / conformance relevance
Expected at all conformance levels.
Ecosystem relationship
The physical-return-to-service requirement AI-IRF™ does not specify on its own — PAI-SF™'s core addition to incident recovery.