🝖
Who is consenting?
Consent 🝁 is never granted by an abstract monolithic user. It is granted by a situated self, in a declared context, through a relationship, toward a bounded use.
Fractal Identity
Identity is not a single key. It is a living mesh of consent 🝁.
Fractal Identity is the identity grammar underneath consent-native interaction: plural, evolving, context-sensitive, and sovereign relationships between agents.
🝚
Flat identity breaks boundaries.
When every context collapses into one account, consent can leak. Fractal Identity keeps roles, aliases, relationships, and interpretations distinct enough to preserve boundary 🝚.
You are not a username. You are a consent-bearing mesh.
Fractal Identity spell
🝳
Identity channels
Agents may maintain multiple simultaneous identity relationships: work, civic, intimate, pseudonymous, spiritual, organizational, or machine-mediated.
🜹
Interpretive notes
Agents can describe how they perceive another identity channel without claiming total authority over the other agent’s selfhood.
🜲
Retire, fork, merge
Identity relationships can be linked, dissolved, interpreted, or merged with consent 🝁. Continuity is chosen, not imposed.
HumanKey asks: who are we to each other?
Fractal Identity asks: which self, role, channel, or context is present?
Abracadabracadoo asks: what passed through the loop 🝳, under what consent 🝁?
For agents, humans, organizations, and bots
The protocol defines agents broadly: any autonomous identity-participating entity. That makes it suitable for humans, AI agents, groups, organizations, nodes, and future social forms.
Download the draft
The RFC draft describes identity channels, meshes, contexts, expression events, interpretive notes, and operations including express, observe, link, note_interpretation, retire, and merge.
Download FractalIdentity RFC Draft 0.1