This is not how hierarchical message resolution is meant to work. The "parentBundle" should be registered as a parent of this component's own bundle, using the member "parents" in the grade fluid.messageResolver - using a hard reference of the type here prevents any further hierarchical decomposition of the message bundle structure, and will become brittle. If necessary we can supply an expander or some other machinery to assemble these values using the messageResolver API into a location in the component where they can be referred to in the protoTree.