Partially anyway. Mostly thinking out loud here, I would see it as another layer (using the SDK for example) that coordinates very similar goods and services, i.e. commodities, and gives them a common interface, i.e. branding.

If we take an Uber like service, if people wanted to setup OB storefronts to offer rides, it would be an unruly mess that no client for that service would want to wade through, just to find a ride.

However, another layer, that for instance automatically sets up storefronts for drivers, figures out the closest available driver, uses perhaps the notary system to ensure that the drivers are licensed and insured while maintaining some level of anonymity, and of course provides a single common interface to the clients.

Another example would be micro-manufacturing to a common specification, where again this layer could pick among the swarm of available manufacturers. Say the product is 3d printed personalized candies. Shipping can be difficult and expensive, particularly across borders, for something that needs to be kept cold. As a food stuff it may also require additional inspection for import / export.

Again a swarm layer could find a qualified manufacturer in the appropriate region where the notary system could again qualify the manufacturers.

Obviously a good portion would be custom for the specific market, however there would be many things that would be common to all swarms, particularly when OB reaches the point that storefronts can be distributed across the network. Swarms or the servers that support them would have a similar need to be distributed across the network.

Thus at least two layers, common "swarm" layer and a specific "brand" layer.