User Hierarchy and Inheritance

The XAI XAPI account system uses a tree-like hierarchy. The goal is not to make accounts more complicated, but to make team, customer, project, and environment boundaries easier to manage over time.

Core Design Philosophy: Holographic Sub-information

The design is inspired by the idea of "Holographic Sub-information." In practice, this means a child account inherits the core governance boundaries of its parent while still operating as its own account.

Within XAI XAPI, that leads to three important outcomes:

• key governance boundaries can flow down the whole account tree
• each level can manage its own descendants
• the system supports delegation without losing control

Parent and Child Accounts

• Parent Account: an account that can create and manage lower-level accounts
• Child Account: an account created by a parent and operated within the parent’s allowed scope

A child account can itself become a parent account, so the system can naturally grow into a multi-level structure. This works well for team collaboration, customer distribution, channel models, and environment isolation.

Genetic DNA

To track the account tree, the system uses a lineage identifier referred to in the docs as DNA.

Its role is not to create extra work for end users. It exists so the system can understand which accounts belong to which branch and which governance rules should flow to which descendants.

Inheritance Principles

The important part of account hierarchy is not individual fields, but the inheritance model:

• a parent can distribute platform capabilities to children
• a child can further govern its own descendants within that allowed scope
• descendants can narrow what they use, but cannot expand beyond ancestor boundaries
• upper-level governance continues to apply downward across the tree

Design Advantages

This hierarchy gives four practical benefits:

1. Clearer organizational boundaries: departments, projects, customers, and environments can be governed separately.
2. More stable policy propagation: upper-level constraints are not easily lost at lower levels.
3. Better delegated management: each level can manage its own subtree without centralizing every action.
4. Long-term scalability: as the business grows, the permission model does not need to be rebuilt from scratch.

Typical Application Scenarios

• Team collaboration: split the tree by department, project, or environment.
• Customer isolation: give each customer an independent branch.
• Channel distribution: let upper levels distribute capability while lower levels run their own operations.
• Multi-level governance: support groups, subsidiaries, and teams within one consistent structure.

In short, the value of account hierarchy is not the fields themselves, but turning governance boundaries into a durable structure.