In a discussion with AP and Song about shipbroker tags, we realized there was a need for a more flexible system.
The following are examples, but we believe that the "broker[scope]" nomenclature is a good nomenclature that is not too bulky or verbose while being easy to understand.

# general
brokerHumanSpace
# regional
brokerNewBeyond
brokerUngovernedTerritories
brokerFrontier
brokerBackroads
# factional
brokerCommonwealth
brokerCorporations
brokerPacificDefense
brokerAIC
brokerNakura
brokerCoalition
brokerYatfwan

Currently the Osaka is set to use these for compatibility with TBR and TSB which will use this system, while also retaining the legacy tags for the time being.
How these are intended to be used is such that:

Say there is a station named "Bob's spaceship emporium" which is an independent shipbroker selling civilian ships that are commonly available throughout human space. You would specify "+brokerHumanSpace; -military;". Lets say that the Osaka, crateship and IAV are ubiquitous designs found throughout human space - if we want them to show up at brokers that sell generic ships, they should have the attribute "brokerHumanSpace" in them. If a modder wants their ship to show up at any shipyard that allows for these generic ships to show up, all they have to do is add brokerHumanSpace to their ship. It wont force its way into every ship vendor, only the ones that add inventory from the "+brokerHumanSpace;" pool.

Say there is a station, the Nakura Shipyard. This is a Nakura corporation shipyard that produces ships like the Osaka. The Osaka is a ubiquitous design, but it also has the "brokerNakura" tag. This allows it to show up in the Nakura shipyard. Similarly, if a mod adds a new Nakura ship, it would just use "brokerNakura" in the ship's attribute tags. This functions most similarly to the existing tags which are unfortunately also liable to be tied to other functionality.