One plane, many bubbles,
cryptographically isolated.

§ 02 · Enterprise NFT Bubble Architecture

A master plane, one enterprise namespace,
one bubble per employee.

The Master corpus is curated knowledge everyone inherits. The Enterprise namespace — minted to a single Enterprise Admin NFT — holds your org's proprietary corpus. Every employee gets a personal User NFT; their bubble tags content with bubble_id and restricted_to_bubbles.

A query from any identity resolves to a namespace filter. No duplicated indexes, no per-tenant Neptune clusters, no cross-contamination.

// The canonical OpenSearch bool filter (UM15 §24.4)
{
  "query": {
    "bool": {
      "must":   [ { "match": { "content": "q2 pricing strategy" } } ],
      "should": [
        { "term": { "namespace": "master" } },
        { "term": { "namespace": "enterprise_de0001" } },
        { "term": { "bubble_id": "team.revops" } },
        { "term": { "bubble_id": "user.elena" } }
      ],
      "filter": [
        { "terms": { "restricted_to_bubbles":
            ["team.revops", "user.elena", "*"] } },
        { "term":  { "privilege_gate_cleared": true } }
      ],
      "minimum_should_match": 1
    }
  }
}