UID Persistence Through Alias Mutation: Stable Identity Across Structural Change
by Nick Clark | Published March 27, 2026
Every indexed object in the adaptive index carries a unique identifier that persists through alias mutations, scope splits, scope merges, and structural reorganization. The UID is the object's durable identity. Aliases are how that identity is found. When the namespace restructures, aliases may change but the UID does not, ensuring that every reference to an object remains valid across the full lifecycle of the index.
What It Is
A UID in the adaptive index is a structurally stable identifier assigned to an indexed object at creation time. It is independent of the object's position in the index hierarchy, independent of the alias paths that lead to it, and independent of the governance scope that currently contains it. When an index scope splits and the object moves to a child scope, the UID remains unchanged. When scopes merge, the UID remains unchanged. When an alias is renamed, the UID remains unchanged.
This separation between identity and location is fundamental. The UID answers the question of what something is. The alias answers the question of how to find it. These are different questions with different stability requirements.
Why It Matters
In systems where identity is tied to location or path, structural changes break references. Renaming a file invalidates links. Moving a database record changes its key. Reorganizing a namespace orphans bookmarks, caches, and cross-references. The cost of structural change becomes proportional to the number of external references, which effectively prevents reorganization at scale.
UID persistence decouples identity from structure. The namespace can reorganize freely because no external reference depends on internal structure. This removes the primary barrier to structural adaptation in production systems.
How It Works Structurally
When an object is created in the adaptive index, it receives a UID that is recorded alongside the object's data. The UID is included in every alias record that points to the object. When the index restructures, such as during a split or merge, the UID travels with the object's data. The new scope creates an alias record for the object that includes the same UID.
Resolution can proceed in two modes: alias-based resolution follows the namespace path stepwise through anchors; UID-based resolution looks up the object directly by its identifier, potentially using a secondary index or distributed lookup that maps UIDs to their current scope location. Both modes reach the same object.
When an alias mutates, the mutation record includes both the old alias path and the UID. This allows systems that cached the old alias to resolve the UID directly and discover the new alias path, maintaining continuity across the transition.
What It Enables
UID persistence makes it safe to restructure a live namespace. Content delivery networks can reorganize cache hierarchies without invalidating client references. Identity systems can rename or relocate accounts without breaking cross-system integrations. Knowledge graphs can reorganize their topology without orphaning citation links.
This property transforms the adaptive index from a static directory into a living structure that can evolve continuously while maintaining referential integrity across every external system that depends on it.
