Identifier Generation Policy (@GV.je System)¶
Each account receives a unique and permanent identifier used for login.\ This identifier is technical and cannot be changed once assigned.
Public identities (actors and addresses such as alice.gv.je) are separate and may change.
Identifier Structure¶
Identifiers follow this format:
Example:
The counter starts at 1 and increases only when necessary to maintain uniqueness.
Source Fields¶
Identifiers must be generated from two explicit fields:
-
Given name for identifier
-
Family name for identifier
These fields are chosen deliberately and should reflect how the person normally identifies their name.
Do not generate identifiers from a single full-name field.
Normalization Rules¶
Before generating the identifier, apply these rules:
-
convert all letters to lowercase
-
remove accents (é → e, ñ → n, etc.)
-
remove spaces, hyphens, and apostrophes
-
transliterate non-Latin scripts if needed
-
keep particles such as de, del, ben, al, van, etc. when they are part of the family name
Examples:
García López → garclope
Ben Ali → benali
Al Hassan → alhassan
van der Meer → vandermeer
O'Neill → oneill
Then apply the 4+4 rule.
Short Names¶
If the given name or family name contains fewer than four letters, use the full available name.
Example:
Counter Rule¶
The numeric counter ensures uniqueness.
Examples:
Identifiers always include a number.
Prohibited Identifiers¶
Identifiers must be rejected if they:
-
contain offensive or inappropriate substrings
-
match reserved system words (for example: admin, system, support, root)
If this occurs, increase the counter and generate the next identifier.
Permanence¶
Once assigned, identifiers must not be changed, except in rare administrative corrections.
Privacy¶
Identifiers are technical login handles and are not intended to be public identities.
Public identities appear through actor addresses such as: