Random ID numbers, or not.

[Spartan159]

While playing at making player ID cards, I looked at identification numbers. What if you had a system to identify *everyone* in the imperium? Tada, you can.

*********************************

# Imperial Citizen ID Format – House Rule

# Encodes origin, birth, social standing, and registry uniqueness

# Format: SSSS-XXXX-YYYY-DDDS-RRRRRR


# ───────────────────────────────────────────────

# FIELD DEFINITIONS



# SSSS = Offset-encoded Sector Coordinates (Base 50 = 0,0)

# - X-axis (Spinward/Trailing): 00–99

# 50 = 0

# <50 = negative (Spinward)

# >50 = positive (Trailing)

# - Y-axis (Coreward/Rimward): 00–99

# 50 = 0

# <50 = negative (Rimward)

# >50 = positive (Coreward)

# Example: 49,51 = (-1,+1) = Deneb Sector → SSSS = 4951



# XXXX = Hex Number (Planetary Location)

# - Format: CC RR

# - CC = Column (01–32)

# - RR = Row (01–40)

# - Subsector derived from hex position (8×10 blocks, grid A–P)



# YYYY = Imperial Year of Birth (e.g., 1105)



# DDDS = Day of Year + Social Standing Code

# - DDD = Julian-style day (001–365)

# - S = SOC code (0–J, skipping I)

# B = Knight

# C = Baron

# D = Duke

# E = Sector Duke

# F = Prince/Princess

# J = HIM (Emperor/Empress)



# RRRRRR = Registry Sequence (6-digit unique ID)

# - Encoded using **eHex+ASCII** logic

# - Supports up to 9.9 trillion unique entries



# ───────────────────────────────────────────────

# eHex+ASCII Encoding Logic



# Traveller eHex uses:

# - Digits: 0–9 (10 values)

# - Letters: A–Z minus I and O (24 values)

# → Total: 34 symbols (Base-34)



# ASCII expansion adds:

# - Lowercase a–z (26 values)

# - Special characters (optional, up to 85 total symbols)



# Combined Base-62 (0–9, A–Z, a–z) gives:

# - 62 symbols

# - 6-digit Base-62 ID = 56.8 billion unique combinations



# Optional Base-85 (ASCII-safe) gives:

# - 85 symbols

# - 6-digit Base-85 ID = 443 billion combinations



# Use Base-62 or Base-85 for RRRRRR to support planetary-scale registries



# ───────────────────────────────────────────────

# EXAMPLE ENTRIES (tab-delineated)



Sector Hex Year Day+SOC Registry ID

4650 1910 1105 273D 00A1Zx 4650-1910-1105-273D-00A1Zx # Lanth, Duke

4951 2307 1099 142B 9fT3Q2 4951-2307-1099-142B-9fT3Q2 # Mora, Knight

5050 0611 1102 001J ZZZZZZ 5050-0611-1102-001J-ZZZZZZ # Capital, HIM

4849 0810 1100 365A 7x9bQw 4849-0810-1100-365A-7x9bQw # Regina, High Status



# ───────────────────────────────────────────────

# Mnemonic Anchor: “Four blocks of origin and time. Six symbols of identity.”

Why yes, I am retired, why do you ask? *Grin*

 

[Terry Mixon]

Is 9.9 trillion entries enough? I seem to remember reading somewhere that the current population count exceeded that.

 

[To Tha Moon!]

That's pretty awesome!

Could you put the Character's UPP with it?

Or would that mess things up?

 

[rinku]

You should include data validation codes, derived from the other numbers to immediately detect errors. Check digits are VITAL for these things. Two or three numerics should suffice.

33 years of Australian government administration has reinforced this point.

Since the 6 character (not number) ID is using upper and lower case alphas as well as numerics, it will be enough for any particular world.
@Terry Mixon the world had already been identified; the unique ID can be the same for individuals who have different homeworlds.

However, administratively it would be useful to record a home registry (maybe sector, but I'd have thought subsector). There are only around 300-400 subsectors in the 3I across 20 or so sectors... You could identify them with two extended Hex digits. Maybe a Sector code, starting at 0 for Core and proceeding in order of 3I Sector precedence - or some other useful Sector identification scheme such as a Two letter designation based on their name in the manner of US states, plus the A-P subsector code. That seems more useful than a sector co-ordinate.

So, let's say the Spinward Marches is sector SM, Regina would be subsector SMC, Glisten would be subsector SMO.

 

[CordwainerFish]

Just use random numbers. If they're long enough there will never be a collision.

 

[rinku]

Sure. But these kinds of things are more useful if they encode metadata as well.

 

[Condottiere]

Birth place, issuing planet, genetic code.

 

[MarcusIII]

Ditch the coordinates and use a system ID# for birth place

 

[MarcusIII]

Not convinced birth system needs to be part of the ID number itself. What happens if it needs to be corrected?

(Rule #5 of working with big data - "hardly ever happens" => "given the volumes, this does happen, so you need to deal with it")

What happens if the birth area code on a Social Security card needs to be corrected?

 

[CordwainerFish]

I have no idea how parochial US systems work. Either the volumes are so small it doesn't happen (unlikely) or they leave it it the same and people who assume a structured code are effed, I imagine.

Very few people know that part of an SSN is based on where you lived when it was assigned, and absolutely nobody actually cares. It's not important.

(Just like my call sign starts with a K and has a 5 in it because of where I lived when I got my license. If I moved I could get a new call sign but won't bother.)

 

[MarcusIII]

I have no idea how parochial US systems work. Either the volumes are so small it doesn't happen (unlikely) or they leave it it the same and people who assume a structured code are effed, I imagine.

So, not a significant problem for either system

 

[Condottiere]

Depends on what you exactly want to pin down.

Birth place tells authorities a great deal about your background.

Issuing planet says when you came into contact with the Imperium.

Genetic code individualizes your identity.

That would match up with database entries that whoever is looking you up is allowed to access, whether military or criminal records, or credit scores.

 

[Condottiere]

Like I said, it depends on what purpose the identification serves.

Highly likely that it's part of a Imperium wide blockchain.

However, there could be variants that wouldn't be part of a complete profile on the character.

 

[Endie]

Yeah, so that becomes just part of the "issuer range" deal, as long as people don't start thinking they can derive useful metadata from it.

My mobile phone number (UK) starts 07956. To those that know, this tells them it was originally issued by Mercury. Even apart from the fact that Mercury got bought and resold, I have twice ported my number, so that that prefix has close to zero useful information now.

Sup fellow mid-90s 07956 number still-possessor.

 

[mavikfelna]

What about those not born on a planet? Or not even in a specific system? My current Aslan character was born aboard ship in the Imperium somewhere Rimward of Core sector. She's not an Imperial citizen but she'd need an ID since she works in Imperial space.

 

[MarcusIII]

What about those not born on a planet? Or not even in a specific system? My current Aslan character was born aboard ship in the Imperium

Then they are considered a non-entity. Forever shunned by Imperial society.

 

[Condottiere]

You can probably register at the next starport.

Could be a requirement for entry.

 

[rinku]

All good discussion, but a check code is still a good idea.

 

[Condottiere]

It comes down to what you want it to do.

If it's also to identify variables, like social standing, it has to be able to tap into a universal database.

Other than that, if you only need it to access something like local or planetary facilities, like your hotel room, a new one can be created, whether or not it's based on an Imperiumwide one or not.

 

[CordwainerFish]

What about those not born on a planet? Or not even in a specific system?

Or in this universe. Some cultures probably have interesting thoughts around those born in Jump.