> How would you design a system that simultaneously achieved all these goals:

> Rapid sending of messages

> Careful checking of the content of messages

> Ability to quickly target a specific geographic area

> Inability to mistakenly send a test message

> Requiring strong proof that the message is authentic before sending

> Resilient enough to work after significant damage to infrastructure

> That networks have the ability to vet and ignore

> That networks are compelled to send

> Which can only be used for good

> And cannot be used for evil.

Considering the last two, I'm assuming this must be tongue-in-cheek.

I think that the best approach for public utilities is to design them in such a way as to minimize, or preclude if possible, their ability to choose their customers or level of service. We want them to have a set of rules/instructions, written beforehand and publicly available, that everyone can point to after an event that says, "well, those were the things they were supposed to do, so they did them." The entities that write the set of rules are separate from the utility: the utility solely exists to implement the rules/instructions as efficiently as possible.

There's obviously a reasonableness factor here: it's impossible to foresee all situations. The effort spent on specifying exactly what should be done should be proportional to the potential impact of that possible decision.