Safety Case Exception Escalation
Objective
Ensure AI-driven hazards not covered by the applicable functional-safety standard are escalated, documented, and approved before deployment or continued operation — not silently absorbed as an unaddressed gap.
Control / requirement
Uncovered AI-driven hazards must be escalated to a named safety authority, documented with compensating controls, and formally approved before deployment or continued operation — this is the enforcement action the gap register (FSI-003) exists to trigger.
Applicability
Any system where FSI-003's gap register identifies a hazard not covered by the applicable standard.
Expected evidence
Escalation records; compensating-control documentation; named-authority approval records. [T2]
Assurance expectation
Evidence that every gap-register entry has either a closed escalation record or an open, tracked status — no gap sits unaddressed without a decision.
Dependencies
PAI-SF-FSI-003 (the gap register that triggers this control).
Exclusions
Not applicable to gaps assessed as having no credible physical consequence.
Maturity / conformance relevance
Expected at all conformance levels — this is the enforcement mechanism that makes Domain 11's mapping controls consequential rather than purely documentary.
Ecosystem relationship
Turns FSI-001/002/003's mapping work into an actual governance decision point — the control that answers "does this domain do anything besides document," per the Founder's requested sharpening.