Product Identity, Names and Aliases

A canonical ID should remain stable even when display titles, spelling conventions or preferred transliterations change. Identity is based on the product represented, not merely on a matching word.

An alias records a supported alternative name, spelling or language form. It does not prove that two recipes, regions or protected registrations are the same product.

Translation and transliteration should preserve meaning and cultural identity while enabling search. Ambiguous terms need language, region or product context rather than one forced English equivalent.

A recipe, process, generic style, regional variant and protected product can be related without being one record. The Codex and Atlas should represent those relationships explicitly instead of collapsing their content.

Generic family hubs can organise regional and protected children while allowing each child to retain its own specification, process and source stack. Shared history should not overwrite legal or technical differences.

Retitles, mergers, splits and redirects need documented reasons and migration rules. Deprecated names should support discovery without recreating duplicate identities or transferring unsupported claims.