Applicable since version: 2.0.0
RuleSets are a two-leveled collection of Rule(s), which is evaluated for an item, to determine if a task, the RuleSet is set up for, should execute its action on it. Saving a RuleSet is merely for the convenience of handing it over to another Profile without having to set it up Rule by Rule. A RuleSet created for a Task does not need to be saved for it to do its job.
Any previously created Rule can be added to an existing RuleSet in one of the two evaluation methods:
Method 1: All rules on this level must apply to the item for it to be taken action on.
Method 2: Only one rule needs to apply to the item for it to be taken action on.
Be M1-0 to M1-n rules from Method 1, be M2-0 to M2-m rules from method 2 with n, m as integers.
So is the combined RuleSet evaluation executed as:
(M1-0 and M1-1 and ... and M1-n) and (M2-0 or M2-1 or ... or M2-m)
With this one or multiple general Rules can be defined in method 1, excluding items from the group of rules defined in method 2. For example excluding all locked items from deconstruction. Of cause this can also be done in a single rule (as it had to be done in RbI Version below 2.0.0), but I noticed that I often defined the same "header" for every rule and had to change it in all rules if I found it to be unsound or not far-reaching enough.