You haven't linked to the specific policy that led to this awful event occurring.
Which specific policy wording enabled this to happen?