Creation Establishes a Permanent Readable Product Identity

Context

A stable common key supports financial and domain references. The implementation uses the readable key instead of a separate editable catalogue code.

Decision

Creation uses a supplied or name-derived readable product key that remains unique across workspace kinds without collision suffixes, with kind and business unit fixed alongside it.

Alternatives Considered

Keep an opaque key and separate editable code. Two identifiers complicate references and differ from the present configuration-key contract.

Resolve collisions by appending a suffix. The service instead reports the collision and requires the caller to choose another key.

Consequences

Changing a kind or business unit requires a new product. Details supported only by unnamed identity guidance remain proposed.