Klever

I expect 3 components of Klever needs to be adjusted to meet a non-standard architecture. They are CIF, CIL and a verifier (at the moment just CPAchecker). I hope that at least for CIL and CPAchecker nothing except some (maybe just one) option will be necessary. As for CIF, cross CIF should be used. Anyway, I do not expect many differences between various architectures. Moreover, we can take into account different aspects of particular projects by describing architecture adjustments separately for all supported project if they need this at all.

That's why I suggest to include a new file called architecture.json which will incorporate all specific stuff corresponding to different architectures into verification jobs and allow users to select one of described architectures within job.json.

If somebody has any objections it would be great to hear them here soon before I will implement the suggested approach.