Extend the concept of Path to Application and Business Layers

It's always been an anomaly for me that 'Path' exists in the Technology Layer, but not in the Application and Business Layers. The BAT Layers look very similar on the whole, with this one exception.

The lack of this concept is circumvented by practitioners through the use of Flow Relationships, but I don't think this is always satisfactory.

• in Business there are many forms of 'network', not the least of which are Social Networks and MS Teams. It would be convenient, on occasions, to show multiple Actors or Roles connected to a single 'Business Path', which has a name.
• in Applications the theme of integration is a highly visible part of the architecture. This could be illustrated through virtual 'Paths'. For example multiple Application sources could be integrated along a single 'Application Path' which is associated to a data acquisition connector for a Data Lake.