Retain Stable Configuration and Product Identities

Context

Imports and other records need stable references even when staff change display labels. Product extensions also need a shared identity across their owning services.

Decision

This record describes the implemented identity schemes. Readable configuration, internal unit identity and product-extension identity serve different reference needs and are not interchangeable.

Alternatives Considered

Generate opaque identifiers for all configuration. That would change direct import and known-record references that currently use readable keys. Allow configuration identity to change with its name. That would require coordinated reference and crosswalk rewriting instead of the existing immutable identity contract.

Consequences

Imports can directly name readable configuration records. Display names remain editable, but an existing configuration identity cannot be renamed. Replacing grants and policies allocates new generated identities; other owned lists use composite keys.