introduced interface ArrayDomain and the Entity implementation 
ArrayEntity, consisting essentially of an Array and a integer index
introduced interface EntityLoaded<T>, providing a load (definition,
value, etc.) associated with the Entity
modified FormStore so that entityForString stores an ArrayEntity for 
each String in a Domain definition (instead of storing the Domain
itself)
using Phrase instead of Claim, introduced the first batch of types
Predicate now has two type parameter, one for itself and one for the 
PhraseFilling with operates upon
A start for an Attribute class
An example of a Structure that simultaneously provides a Category and 
Predicate (expressing the same concept), each of its own definition
starting a new approach for phrase
renamed Phrase to Phrase0 and moved it to package phrase0
a new embodiment of phrase;
started to use the essence pattern
noted that the CompositePhrase.Essence inner class is (almost) identical
to CompositePhrase, so I replaced and removed it.
Some complementPhrases; started to insert Basic implementations into 
interface declarations
not all Phrases (Entities) are defined by a stored field essence(),
some are defined by their structure. So we renamed Complement to 
EssentialComplement to indicate that this particular type is defined by
an essence() field.....then renamed it again to AtomicComplement.
And the changed Phrase to AtomicPhrase as well
used the AtomicEntity essence pattern here and there
extracted Basic (then renamed Impl) and Complements (not generic any
more)
from CompositePhrase;
Created ComplementsOnCollection;
added compose() method to Predicate