Current thoughts, eLindaTupleSpace

I think Module imports and parent, vat pending continuations and vatSemaphores and scope-encrypted wiring and running priority stacks and the tuners agents, the transceivers, all are managed through an eTupleSpace as the roots of storage with ephemeral registration in module definitions. Chain a break reactor to uncouple. I am not sure how this rests in design, a start to integrate with tracing added. Welcoming comments. These thoughts to prep for ASN1 to substitute through the scope, or through eLinda.