This in part a way of addressing shorter-term the current lack of sub-patching support, but has standalone value in managing complex patches, and can also serve as a way of identifying (ear marking) collaborating nodes as candidates for sub-patching.
It would be really convenient to be able to visually and graphically contain patch nodes in a completely passive (parasitic) container box with a name/title. To move the nodes, one would simply move that container box. The name can serve to identify the collaborating role of the contained nodes.
The container would not itself have inlets/outlets (ports), and would not participate in signal transfer.
Longer term, users could then choose to sub-patch such a container from a context menu item (promote a candidate group of nodes that perform some well defined collaboration to achieve a goal/idiom).
It should also please (this is very important) by nestable! It should be possible to have sub-groups of nodes within a parent group, and so on.
Some Wire example patches show a Comment, without any actual grouping of nodes, just as a visual indicator behind the visually "contained" nodes. This is completely inadequate.
Related: Wire: Desperately needs sub-patching (reuse of groups of nodes in another context with inlets and outlets)