Thanks to the contribution of Doc Mud it is assumed now that it is possible to use genetics algorithm to translate info unit chains into "generations". It will also possible maybe to decouple the virtualized swarm made of info units, from the visitor that will explore units tp apply composition logic. In this way it will be possible to do somethinf very interesting: change the translation analysis context keeping the same info unit (bees and bees chains) producer. I try to explain:
Informations producer is always the virtual swarm made up of info units priduced by virtual devices.
The information consumer is the logic using the swarm of inormation unit to compose the system knowledge base shape (called shape as we like to think to this code object as a 3D space reshaping every time it is enriched with experience).
Delegating to a proxy between the info producer and the info consumer, the logic used to manipulate available info units to enrich a knowledge base can be changed without redrawing the info producer. Less system parts to rewrite in case of error, more time earned. Hmm more than a computing model can be applied to the swarm in order to make comparison and change the system computing model. It will be necessaru ti ad some more drawing.
Recap on the fly:
Physical devices are abstracted by the virtual world, via an HAL impl.
Every real device is forwarded inside the reality of the virtual world via a virtual device alias, to decouple, generalize, allow testing and data mutation/inijection
Every device alias has n channels, one for each port it has on the physical device it is mapping. Every device alias is registered in a suitable logic repository.
Every channel is registered in a repository, almost the same it happens for virtual devices.
At a t time, the system read all the channels that are INPUT capable, as all the channels "observe" the same observer-notifier.
This, via the channel repository, will cause all the virtual device channels to wake up, read (if they can) and communicate a generalized and channel and device independent DTO, keeping the value found and the read metadata.
All these infos-DTO will be a shot of the system
Every inofmation unit generated and part of a shot will be activated becoming a bee of a virtual swarm in a virtual beehive.
When an information unit DTO is activated (let's say because it implements a Runnable paradigm as well), it becomes a bee too.
Polymorphism on info unit makes it possible that an info unit is also a thread worker and when activated is it a bee.
This is the information producer subsystem
A proxy for the bee swarm computing logic act with bee creating info units/bees and hiding the algorithm build a polymer of informations/bees that cause the system knowledge base to reshape. System knowledge base is enriched by an hidden login working with the virtalized swarm.