existential/quantity rules

How the negation will be handled ? An easy solution is to forbid negation condition as first condition or, at least, to have non negational condition in the rule. Otherwise when a rule with only negation condition will occur ? At the very begining of the working memory or after the first fact is asserted (provided the rule could match) ?

<bob> 47 means, firing a rule when there's, let's say, 15 people who have the same birthday as you
<bob> or more importantly, when there's 0 people with the same bday
<conan> ok your talking about a "count" method to see how many times a rule is matches - for 47?
<bob> 47 is more about existential rules
<bob> post 2.0
<bob> so you can write rules like:
<bob> if:
<bob> a package does not relate to any truck
<bob> then:
<bob> ...
<bob> without having to do package.getTruck() == null
<bob> post 2.0, can't think about it right now
<conan> ok I have been talking about that. I want to be able to specify a condition an get a count on it then have it return true if the count == my given amount.
<conan> that the same thing?
<bob> more like
<bob> rule(Person p)
<conan> great need that for GAs
<bob> if:
<bob> p.getName().equals( "bob" );
<bob> then:
<bob> thisRule.incr();
<bob> and being able to test the # of times that rule has matched
<bob> and use it in other rules
<bob> ie,
<bob> <condition>peopleNamedBobRule.matches == 3</condition>
<bob> so we can tell there are 3 people named bob in the memory
<bob> w/o having to have 3 extra Person param and 3 conditions testing for bobness
<bob> or something
<bob> post 2.0