Verification requirement policies

[JoselleAstrid]

In this system, when a record is submitted to FZC, a few automatic checks would be run to see if the record requires verification to qualify for any of the applicable ladders. If any of the checks apply, then the record does not appear on ladders until it's verified.

Possible conditions for requiring verification include the following:

• 1st place, top 5, top 10, etc., perhaps depending on the ladder
• Records that were played on emulator

Details which I think would be best for simplicity/clarity (but leaving these points open to debate still):

• If an unverified record requires proof on one ladder but not another, then it won't appear under either of those ladders. This way each record only has two possible qualification statuses on FZC, qualified or not qualified. Not "qualified under this ladder/filter set, but not this ladder/filter set". If a record hasn't qualified, then it'll only be viewable under the archive view. (Not sure if 'qualified' is the best term here, but hopefully the idea's clear enough.)
• The verification conditions are only checked at the time of submission. So if top 10 requires verification, you submit an 11th place time, and then someone ahead of you gets disqualified, then your record doesn't suddenly require verification to appear on the ladders.

Database details:

• The verification policies would probably be saved per ladder. For a start, we can implement the two types of policies we need, "within top N places" and "falls under this filter-spec". Actually, the current Climax policy is a combination of the two, so we have to say "within top 10 AND platform is emulator".
• Each record would have a true/false flag saying whether it qualifies for ladders or not. On submission, it's set to true or false depending on whether the verification policy applies to the record. Verification sets the flag from false to true. If a problem is found later with the proof, or some other problem casts doubt on the record, then a mod can set the flag from true to false. This should probably be a separate field from the verified field, since a record can be unverified and still qualify for ladders. Alternatively it can be a single field with 3 statuses: verified, unverified but qualified, unqualified.