Violation Handling

[asofold]

Peculiar topic, more area to be covered, note that notifications might be another split topic, just to remind:

Basic demands are:

• Some severity judgment.
• Scale: can the violation be expressed in numbers at all (if so, is it a linear scale or not, how do the numbers behave with repeated violation?).
• Type of violation: one-time special judgment (self-hit, illegal position, ...), something done too often/far (though uncertain if continued),
• Probability for false positives / nature of check.
• Probability for follow up violations / nature of follow-up false positives.
• Generalized violation handling / judgement: not to need to implement same schemese over and over .
• General simplified judgment about severity level (to enable global switches, one of the fancy to have points).
• Detect repeated violation, even if staying with low levels.
• Detect loops (also having false positives in mind, probably for the statistics part, though should probably come before notifications handling).

We should make selection in a file: what we absolutely need for a first "step-in" version and what we want to keep an eye on for later - so decide for a basic design for lift-off that allows for future additions of the wanted kind.