Absorbed Identity

The Lifecycle

Transitions Explained

An alias distinguishes an absorbed identity from an ordinary missing record. Record routes report the merge and destination, and a later merge rewrites incoming aliases directly to its survivor while retaining original attribution.

What Cannot Happen

The application cannot erase aliases or recreate an absorbed identity within the same workspace and type. Workspace lifecycle owns privileged removal.

Concurrency and Timing

Alias writes share the successful transaction, but destination liveness is incomplete. Ordinary survivor deletion can leave a dangling alias, as the planning findings already record.