Or, have a “relevance killer” statement, i.e., the relevance is something like “not exists /var/opt/BESClient/ignore/site-content-XXXX.lock” where you can substitute ‘content’ for fixlet, task, or whatever - where XXXX is the ID of the content. Adding ‘site’ label is, of course, optional.
When you need to stop the policy (because you are working on it) you need to merely touch a file with the correct name. And remove it to restart the policy. More automation is always possible.
Thanks @SLB - for an idea I understand!