anchor.diff:  assertEquals( 0, list.size() );
   ----
   
  -==== RuleUnit identity
  +=== RuleUnit identity
   
   Since a rule can guard multiple rule units and at the same time a unit can be guarded and then activated by multiple rules,
   it is necessary to clearly define what is the identity of a given unit. By the default the identity of a unit is simply the
  
positive.code: ----
  [Mario>4, Sofia>3, Mario>3]
  ----
  
  == Breaking changes
  
  The KieSession option to control when timed rules have to be automatically executed has been renamed into `TimedRuleExecutionOption` fixing a typing mistake in its name which affected previous releases; the property has been aligned into `drools.timedRuleExecution`.
  
  [cols="3", options="header"]
  .Name changes
  |===
  |
  |previous releases
  |version `7.0.0.Final`
  
  |KieSession option
  |`TimedRuleExectionOption`
  |`TimedRuleExecutionOption`
  
  |property
  |`drools.timedRuleExection`
  |`drools.timedRuleExecution`
  |===
  
negative.code: persons.delete( marioFh );
  ----
  
  === Imperatively running and declaratively guarding a RuleUnit
  
  As anticipated, multiple rule units can be defined in the same knowledge base and these units can work in a coordinate way
  by invoking or guarding the execution of each other. To demonstrate this let's suppose having the following 2 drl files
  