Yes, good catch. Refactored this a bit to issue two developer warnings: "the type of the policy is invalid" and "the policy is invalid". Giving developers more information on how they're screwed can't be bad, right?-) Alternatively, we can fold the two warnings into a single generic "you're screwed" warning too.