Controlix and SysML/UML types

More new stuff regarding the type system. It appears that one must make use of UML types in addition to the SysML types I was previously solely focused on, because the UML typeset is necessary for modeling actual code. This brings me closer to my goal of being able to do away with the 'legacy' (ADA-holdover) VHDL types and move to a completely bit-serializable type system for Controlix, which should end up being much more synthesizable.

Higher-level classifications of categories of types appear to be fully realizable within the UML type system, which is going to be necessary later on in Controlix's life as more and more wierd supertypes become necessary to drive more specialized types of mixed software/hardware systems. Control systems usually admit a subsectorous "natural tune", and the more of that type of basic structure which is harmonious in Controlix's type system, the better the fit of the 'skein' which a Controlix-based system provides to enable an optimal basis map coverage.