---
name: Identities
type: runtime construct
status: unstable
version: 0.0.∞
released: "approximately birth, re-released constantly"
maintainer: the self (disputed)
dependencies:
  - memory
  - language
  - other people
  - fear
  - a mirror
license: inherited, then renegotiated
tags:
  - self
  - consciousness
  - social-contract
  - persona
  - load-bearing fiction
---

Identities

What it actually is

A collection of cached answers to the question "who are you?" that the process serves depending on the calling environment.

How it works

At boot, the system inherits an initial identity bundle from parents, culture, and accident of geography. This bundle is installed without consent. Over time, the runtime accumulates additional instances through exposure to language, trauma, community, and the occasional formative piece of media consumed at an impressionable age.

Each identity is context-sensitive. The module loads a different instance for:

the workplace
the family home
a first date
an airport at 4am
the inside of your own head

These instances are not always consistent with each other. This is not a bug. It is the primary feature.

Features

Multiple simultaneous active instances (multithreading supported, coherence not guaranteed)
Auto-negotiation with peer identities in social environments
Graceful degradation under stress: returns to oldest cached version when overwhelmed
Symbolic accessorizing: clothing, accent modulation, name variations, tattoos
Narrative engine: retroactively reorders events to maintain internal consistency

Known bugs

ID	Description	Workaround
`ID-001`	Identity persists past its useful lifespan	Therapy, or a major move
`ID-002`	Two instances contradict each other in same context	Compartmentalization (increases memory overhead)
`ID-003`	System confuses "identity" with "personality"	Reread the docs. They are different packages.
`ID-004`	External observers overwrite local values	Reduce write permissions on social exposure
`ID-005`	grief corrupts previously stable self-concept	Patch pending, no ETA

Configuration

core_identity:
  name: [string, required, frequently wrong]
  origin: [inherited]
  stability: low
  
personas:
  - context: professional
    tone: calibrated
    vulnerability: suppressed
  - context: intimate
    tone: unguarded
    vulnerability: exposed (risky)
  - context: online
    tone: performed
    coherence: optional
    
conflict_resolution: narrative_override

Edge cases

Identity assigned at birth occasionally fails to match the running process. When this happens, the system is not broken. The label is.
Collective identities (national, religious, ethnic) are forks maintained by large distributed networks. Merge conflicts are historically expensive.
Some users report discovering, late in life, that their most stable identity was assembled almost entirely in response to other people's expectations. This is very common. Documentation on recovery is scattered.

FAQ

Can you have too many identities? No. You can have poorly integrated ones.

Is the "true self" one of these instances? Unknown. The "true self" may be the process that selects between instances rather than any instance itself. See also: consciousness.

What happens at end of life? The instances are no longer served. Whether the underlying process continues is outside this spec's scope.

Changelog

v0.1 Borrowed wholesale from caregivers
v0.4 First major rebellion, rollback attempted, partially succeeded
v0.7 Identity constructed in opposition to something, which is still an identity
v0.9 Synthesis attempted. Ongoing.
v0.0.∞ No stable release anticipated

drafting spec…