anchor.diff:  
   == 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
  +As anticipated, you can define multiple rule units in the same knowledge base and these units can work in a coordinated way
   by invoking or guarding the execution of each other. To demonstrate this let's suppose having the following 2 drl files
   each of them containing a rule belonging to a distinct rule unit.
   
  
positive.code: end
  ----
  
  Here the persons matched by the left hand side of the rule comes from the ``DataSource`` contained in the RuleUnit class with
  the same name, while the ``adultAge`` variable is used in both the left and right hand side in the same way as it was a global
  defined at drl level. In other words the ``persons`` DataSource acts as a specific entry-point feeding the working memory.
  
  The easiest way to create a ``DataSource`` is using a fixed set of data as in:
  
  [source,java]
  ----
  
negative.code: It is not allowed to mix rules with and without a rule unit in the same KieBase.
  ====
  
  Additionally, you can rewrite the same pattern in a more convenient way using the oopath notation introduced in drools 6
  as shown below:
  
  .A rule belonging to a rule unit using the oopath notation
  [source]
  