chunks being built despite justifications in backtrace when creating result on super-superstate

If the backtrace for a result created on a superstate encounters wmes that
are supported only by justifications, the current (and correct) behavior of
Soar is to not create a chunk for the result. This is because a chunk would
depend on the presence of non-reloadable justifications that are not going
to stick around.

However, if a rule that tests ^quiescence t creates a result in a
super-superstate, Soar's behavior will be different and arguably incorrect.
Soar will first create a justification that is supported by the immediate
superstate. Then it goes on to backtrace through that justification and
create a chunk that fires in the super-superstate. Since this second
backtrace traces through a justification, it should create a justification
rather than a chunk, according to the logic in the previous paragraph.

I've attached two test cases, one that exhibits the correct behavior
described in the first paragraph and one that exhibits the incorrect
behavior described in the second paragraph.

Original issue reported on code.google.com by joseph...@gmail.com on 5 Apr 2010 at 9:27

Attachments:

sleyzerzon / soar

chunks being built despite justifications in backtrace when creating result on super-superstate #65