Context: Confluence is divided into multiple spaces, and in many organizations each space defines its own bounded contexts, each with its own set of terminologies and definitions. This can make the "define" functionality a completely new set of problems and a source of confusion when it sources answers across all of the organization.
Example: In an API Architecture space, the term "consumer" would specifically refer to an API consumer, perhaps defined by a web client. In a product-focused space, the term "consumer" represents an end user who purchases a product.
Question: Is it possible to define any kind of boundaries around Atlassian Intelligence? Or perhaps is there any kind of weighting mechanism that prefers local definitions over others; i.e. can I improve definitions by creating a page of terms within a space?
