this is also on the list... in its current state, I don't think there is any reason the child module's need the parent context (which only contains the "input" and/or "output" channels really) to be their parent. Instead they are getting the parent (xd-common) set directly in the Module initialization code. I left this there as a reminder that we might need to think thru this, especially if the context available here could play a bigger role. It may be related to the properties passing thru if nothing else.