Klever

At the moment it is possible to develop verifier profiles for different architectures but it is inconvenient due to users need to duplicate all required verifier profiles giving them new names and changing the same options (most likely). Besides, one should select new profiles within a requirement specifications base.

We assume that it is possible to specify particular options for particular tools and architectures globally, e.g. for top-level templates, so that all child templates and verifier profiles will be configured without any efforts. In addition, users will not need to change anything in the requirement specifications base. The only thing to do is to specify "architecture": "NAME" within job.json.

You should keep in mind that nobody will prevent users for setting individual verifier profiles as usual. So, if some specific settings will be necessary ever, everybody is welcome.