Wow, holy smokes, thanks! I'm going to have to read this one over a few times to really understand it fully.
You mentioned predicting ultra-rare events. I wanted to give you a lovely story along these same lines though. Remember the TJX credit card system theft (TJ MAxx, Marshalls, Winners, HomeGoods, ...)? Last month, the fraud group asks if I can build a statistical model to predict the next time a hacker will break into a store's database, and if so, which store. Any advice? I've already tried using chicken bones, tea leaves, and measuring the rings around Uranus. Did I miss something? I don't think the fraud group appreciated me telling them that they were smoking crack and SOL on this one.
You forgot to ask the Oracle 9i of Delphi.
How's this:
You sell 'em a "system" that is you claim can predict the hack attacks. Charge them by the month to operate the system, and pay me half the monthly take. The system consists of me telling you which store I'm going to attempt hack in the coming month. You recommend that that store take extra precautions, including ones which will cover the details of the attack I'm planning (and which I"ve given to you.) Those precautions block my attack and document the attempt.
You make money, I make money, and the credit card folks are happy 'cause they've got a system that predicts and blocks data theft - and if a real attack gets through somewhere, then that's just tough. [Rule 8] happens, and they know that no system is perfect.