Since you've touched the of sending |map 0, map 1( from an abstraction to it's parent¹ allow me to ask this in the dev list:

The only way i know only with vanilla objects is to use a [namecanvas] on the parent and pass it's name as an argument or through an inlet. Do you (or anyone reading this) happen to know a more elegant way? Perhaps something new recently introduced under the hoods in the latest PD releases, idk

Cheers,
Henri.

¹  https://forum.pdpatchrepo.info/topic/9454/full-support-for-gop-dynamic-patching   (putting it here since it wasn't present in the replies below)

De: Pd-list <pd-list-bounces@lists.iem.at> em nome de Alexandre Torres Porres <porres@gmail.com>
Enviado: sábado, 10 de novembro de 2018 20:27
Para: Pd-List
Assunto: Re: [PD] naming a parent patch: is this external useful?
 
For the record, I guess I should have said I'm deciding to forget about adding such an object to my library, since [sendcanvas] already takes care of this (so we don't need yet another one) and also cause I can deal with this inside the abstractions of my library with vanilla objects anyway...

sorry for the noise

Em sáb, 10 de nov de 2018 às 19:56, Alexandre Torres Porres <porres@gmail.com> escreveu:
Em sáb, 10 de nov de 2018 às 18:13, Alexandre Torres Porres <porres@gmail.com> escreveu:
it would probably exist somewhere, specially in [iemguts] of all places, but I couldn't find this functionality there (or I just missed it completely).

yeah, I should have looked more carefully, at first glance I missed it completely, but I dug in more deeply, object one by one, and found out that iemguts has a [sendcanvas] object which also does that :) 

so yeah, apparently this is a useful feature for one reason or another...